Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

False Positive in magento-coding-standard #420

Open
drinkingsouls opened this issue Aug 1, 2023 · 0 comments
Open

False Positive in magento-coding-standard #420

drinkingsouls opened this issue Aug 1, 2023 · 0 comments

Comments

@drinkingsouls
Copy link

drinkingsouls commented Aug 1, 2023

Hi Maldetect

Sometime since my last full scan which was last week, I've noticed two files being flagged as malware yesterday.

malware hit {CAV}Php.Backdoor.Generic-10006641-0 found for /vendor/magento/magento-coding-standard/Magento2/Tests/Functions/DiscouragedFunctionUnitTest.inc

maldet(7084): {hit} malware hit {CAV}Php.Backdoor.Generic-10006641-0 found for /.cache/composer/files/magento/magento-coding-standard/5cf0da126fda162c53eba8037babc7efd1dae3a9.zip

These are standard Magento files. I reinstalled the entire vendor folder and rescanned and it still flags in Maldetect. The exact same files don't flag on my site clone.

This is believed to be a false positive via Magento. See issue #460

My question is:

Why would an unchanged file that was not flagged previously start now?
Why does it not flag on my clone site?
The files are identical. If I replace one with the other it still only flags on one server and not the other.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant