wp-malware-removal
Skill33 starsChanged 4 months agoAGPL-3.0View on GitHub
Forensic-grade WordPress malware detection and removal that catches the stealth infections a typical scan overlooks. Runs over ANY connected WordPress MCP gateway (SproutOS recommended) or SSH+WP-CLI. Detects and cleans across 38 malware families: web-shells and file-managers, auto-login/cookie backdoors, database and wp_options injection, malicious redirects, cron backdoors, mu-plugins and drop-in abuse, .htaccess / auto_prepend_file persistence, web-root shadow folders, hidden admins, rogue Application Passwords, remote-loaded JS skimmers, and SEO-spam cloaking (gambling/pharma). Sees the site the way Google and an attacker do — not just as a browser. Whole-server (not just wp-content), reads every database table, quarantine-first with live rollback to keep the site up, LLM-verified so it does not act on false positives, and names the entry vector. Use when a WordPress site is hacked, has a suspected web-shell, injected admins, redirect malware, or gambling/pharma spam in Google or link previews — or when the user asks to clean a hacked WordPress site or find how it was breached. For a read-only "how hackable am I?" check use wp-security-audit; to lock the doors after, use wp-hardening.
In this repository4 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- wordpress-malware-removalSkill
- wp-hardeningSkill
- wp-security-auditSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.