- Home
- Skills
- APIs & Backend
- WP Security Audit & Malware Cleanup
Works with the AI Agents you already use
WP Security Audit & Malware Cleanup
Systematic WordPress security audit and malware cleanup methodology. 4-phase process covering core integrity, rogue admins, backdoor detection, and safe remediation with rollback.
$9
WP Security Audit & Malware Cleanup
Example session with this skill installed
My client's WordPress site has hidden casino links appearing in Google search results but they don't show when we visit the site normally. Can you audit the site and clean it up?
- Read your context and instructions
- Compiled the wp security audit
Security audit: cloaked SEO-spam injection
This matches a known malware pattern (conditional link injection visible only to Googlebot). Starting the 4-phase audit.
Phase 1 findings
| Check | Result |
|---|---|
| Core checksums | 3 files should not exist in wp-admin/ |
| Plugin checksums | "WP Link Helper" (no author, v0.x) not on wordpress.org |
| Admin accounts | 2 duplicate-login admins with empty emails |
| Application passwords | "Dorgen Panel" on rogue admin, "auto-bootstrap" on YOUR admin |
| .htaccess | Clean (force-HTTPS only) |
| Cron | wlh_health_event present (malware recovery timer) |
Phase 2 triage
This is the
WP Link Helper SEO-spam backdoor. It hides from the Plugins screen, injects casino links for Googlebot, and self-heals via mu-plugin recovery. Kill order matters.
Phase 3 cleanup plan (needs your approval)
- Deploy blocking mu-plugin (000-block.php) to disable self-heal
- Quarantine: plugin files + 2 mu-plugin copies + 3 planted core files
- Delete 2 rogue admins (reassign content to your account)
- Revoke 3 application passwords (including the one on YOUR account)
- Clean wlh_* options and cron event
- Shuffle salts, clear sessions, reset your password
Shall I proceed with step 1?
Connects securely to your tools. The creator never sees your data.
About this skill
What this skill does
A complete, field-tested methodology for auditing WordPress security and cleaning up after compromises. Built from dozens of real-world malware incidents on production client sites. Every procedure includes safe rollback.
The 4-phase process
Phase 1: Reconnaissance
- Core file integrity verification (wp core verify-checksums)
- Plugin/theme checksum validation
- Administrator account audit (detects direct DB injection, backdated accounts)
- Application password scan on ALL admins (catches passwords planted on legitimate accounts)
- .htaccess review for hijacks and redirects
- Database injection scan (posts, options, cron events)
- Known malware signature matching (WP Link Helper, core-mimicry backdoors, fake plugins)
Phase 2: Triage
- Classifies every finding: planted files, modified core, rogue accounts, app passwords, script injections
- Identifies confirmed false positives (vendor tracking pixels, debug logs, force-HTTPS redirects)
- Separates leads from proof with verification steps
Phase 3: Cleanup (order matters)
- Neutralize self-healing backdoors BEFORE removing anything
- Quarantine files (not delete) for safe rollback
- Remove rogue admin accounts with content reassignment
- Revoke compromised application passwords
- Credential rotation with side-effect protection (e.g., Smash Balloon Instagram token preservation)
- Core reinstallation if needed
Phase 4: Post-cleanup
- Hardening recommendations (XML-RPC, auto_prepend_file, monitoring)
- 48-hour monitoring checklist for reinfection detection
- Independent verification from external IP
Reference files included
- Malware signatures: 6 documented malware families with identifiers, behavior patterns, and kill procedures
- False positives: 5 confirmed-legitimate findings that scanners flag incorrectly
- Cleanup checklist: Step-by-step printable checklist with dependency ordering
Who this is for
- WordPress developers responsible for client site security
- Agencies managing multiple WordPress installations
- Freelancers handling post-hack cleanup
- Anyone who got the "your site has been compromised" call from a client
Works best with
This methodology can be executed manually via WP-CLI and database access. For automated scanning with all checks built in, it pairs well with Claude Connector, an MCP-based WordPress management tool that provides security scans, quarantine, .htaccess review, core file diffing, and core reinstallation as agent tools.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Requires WP-CLI and SQL access. Premium/custom plugins without remote checksums require manual review. Does not support non-WordPress sites.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 16 days ago
Permissions
File Scopes
Reads its own reference files (malware signatures, false positives, cleanup checklist). Terminal/shell is needed to run WP-CLI commands and database queries during the audit. No network access or file writes to the skill itself.