This project is a security tool, so a way to get malware past it is a vulnerability. Please report these privately, so a fix can be ready before the details are public:
- a sample or a technique that the rules miss but should catch (a false negative or an evasion)
- a way to make the scanner execute, modify or send something from the files or the dump it reads
- a way to make it print secrets, unsanitised text or control characters
- a way to make it hang, run out of memory or crash on a crafted input
Use GitHub private vulnerability reporting: open the repository's Security tab and choose "Report a vulnerability". The repository is https://github.com/CodeVertex55/wp-malware-scan.
Please include:
- the version (
wp-malware-scan --version) and your Python version - what you did and what you expected
- a minimal input that shows the problem
Do not attach working malware. Describe the sample, or send a defanged version with the active parts replaced by placeholder text that still triggers the problem. Do not send real credentials, real site content or anything that belongs to a third party.
This is a small project maintained by one person. The maintainer will acknowledge a report as soon as possible and will tell you where the fix stands.
- A false positive. Please open a normal issue with the rule id and, if you can, a harmless example of the legitimate file or option.
- A missing rule for a threat the scanner never claimed to cover. See the limitations in the README. Ideas for new rules are welcome as normal issues, unless the idea is itself an evasion that should stay private.
Only the latest release gets fixes.