Malware scanner, core integrity checker, auto-repair, database cleanup, quarantine, file permissions, user audit, find and replace, health check, and password reset.
A scanner that reports a modified core file leaves you to work out what changed and what to do. Comparing against real WordPress checksums and repairing from source is the part that ends the problem.
Verify every core file against the official WordPress checksums, then repair from source.
Scan files and the database for the patterns that matter, with the findings explained.
Suspicious files are isolated rather than destroyed, because false positives happen.
Find accounts that should not have the access they have.
Check file permissions and force password resets after an incident.
Cleanup, health checks and careful find-and-replace across the database.
Ask what is wrong and the agent scans, explains what it found, and repairs what should be repaired — rather than handing you a report to interpret.
Verify core, quarantine what does not belong, audit users, reset passwords.
Find out what the last developer left behind before you take responsibility for it.
Cleanup and health checks on a schedule rather than when something breaks.
Check who has administrator rights and whether they still should.
Security & Maintenance is built into NibWP and gives any MCP-compatible AI agent — Claude, Cursor, Claude Code and others — the tools to inspect and repair a WordPress install.
Detection on its own is rarely the hard part. Being told that three core files differ from the official release leaves the real questions open: which files, what changed, and what should be done about it. Verifying against WordPress’s own checksums and repairing from source answers all three.
Suspicious files are isolated rather than destroyed, because a false positive that deletes a working file is its own kind of incident. Genuinely dangerous operations — database find-and-replace, forced password resets — are flagged destructive and gated accordingly.
| Tool | Type | What it does |
|---|---|---|
| nibwp/security-verify-core | read | Verify core files against official WordPress checksums. |
| nibwp/security-repair-core | write | Restore modified core files from source. |
| nibwp/security-scan-malware | read | Scan files for malware patterns. |
| nibwp/security-scan-database | read | Scan the database for injected content. |
| nibwp/security-quarantine-file | write | Isolate a suspicious file without deleting it. |
| nibwp/security-audit-users | read | Audit users, roles and capabilities. |
| nibwp/security-file-permissions | read | Check file and directory permissions. |
| nibwp/security-health-check | read | Overall health of the install. |
| nibwp/security-cleanup | write | Clean up leftover and unnecessary data. |
| nibwp/security-find-replace | write | Find and replace across files. |
| nibwp/security-db-find-replace | destructive | Find and replace across the database. |
| nibwp/security-change-passwords | destructive | Force password resets across accounts. |
No. Security & Maintenance is built into NibWP and available on every plan, including Free.
No. This scans, audits, repairs and maintains. It does not sit in front of your site blocking traffic, and you should still run whatever protection you already trust.
It is quarantined, not deleted — isolated so it cannot run, and recoverable if the detection turns out to be wrong.
Database find-and-replace and forced password resets are flagged destructive and sit behind a permission an ordinary read-and-write connection is never granted.
Activate the integration and it's live on your MCP endpoint instantly.