What is this tool used for?
This is a practical checklist for teams handling a WordPress website suspected of being attacked. It guides users through 3 stages: responsibility confirmation, diagnosis using local AI scan, and incident handling in a logical order. Each step includes a brief explanation and sample prompts for the AI Agent to directly read source code, database, or access logs.
Why use an AI Agent to scan WordPress malware?
Most WordPress incidents are not located in a single file. Hackers may insert backdoors into themes, hide shells in uploads, create new admin users in the database, or attach redirects in options. Manual inspection can easily miss issues due to the large amount of data. AI Agent helps quickly read the entire local workspace and summarize suspicious points in a structured format.
Main process in the checklist
Key differences of the tool
This page not only lists tasks. It also tracks processing progress, provides ready-made sample prompts, suggests priority files and database tables, and helps the team not forget important steps such as changing database passwords, checking cron jobs, or re-verifying Google Search Console after cleanup.
When to use?
cPanel: Similarly, switch back and forth.
• uploads/ — find hidden .php files in images/media
• themes/ — both active and inactive themes
• plugins/ — all plugins, including deactivated ones
• mu-plugins/ — the most commonly overlooked location
• Drop-in files: advanced-cache.php, object-cache.php, db.php
Copy everything, paste into wp-config.php replacing the old section.
find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;
chmod 600 wp-config.php
• Home page loads normally, no red warnings from Chrome/browser
• Access a few content pages, no strange redirects
• Able to log in to WP Admin
• Main functions (form, menu, search) work correctly
• Check on mobile



