| 开发者 |
themepaste
habibnote |
|---|---|
| 更新时间 | 2026年5月12日 21:22 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp-content directory, detects backdoors, cleans injected site scripts, fixes redirect hacks, and triggers malware auto-purge — all from your WordPress admin dashboard with no external service, no subscription, and no data ever leaving your server.
Whether you're dealing with a live attack, a hidden backdoor, or a redirect hack silently sending visitors to malicious sites, Deep Malware Cleaner gives you the tools to scan, alert, and act — fast.
Core Capabilities
Deep Cleanup Scan
Walks your entire wp-content directory, inspecting every PHP file for known malware signatures, obfuscated code, and injected payloads. Results are sorted by severity so the worst threats surface first.
Backdoor Fixer
Detects PHP backdoors uploaded through vulnerable plugins or themes — including webshells, remote-execution scripts, and hidden PHP files inside the uploads folder where no PHP should ever exist.
Site Script Cleaner
Identifies injected JavaScript and malicious <script> tags, hidden iframes, and obfuscated code blocks embedded in your theme or plugin files.
Redirect Hack Fix
Flags the PHP patterns most commonly responsible for redirect hacks — including header() injection, variable-based shell execution, and compressed payload backdoors used to silently redirect visitors to attack sites.
Malware Auto-Purge
Remove confirmed threats directly from the scan results screen without touching FTP or cPanel. Quarantine or delete flagged files in one click.
Login Protection
Hardens your WordPress login against brute-force attacks and unauthorized access attempts — an essential layer of website protection alongside active scanning.
Instant Alerts
Get notified the moment a scan finds a threat. Real-time alerts keep you informed so you can respond before an attack escalates.
What the Scanner Detects
shell_exec, passthru, proc_open, popen, and system called with a variable, a classic attack pattern for remote code execution.<iframe> elements injected with display:none used to load malicious content invisibly..php file in wp-content/uploads/ is flagged High severity; legitimate uploads are never PHP files..pot file included.No. The scanner runs only when you click Start Scan in the admin. It does not hook into page loads or run any background cron jobs. Visitor-facing performance is completely unaffected.
The scanner reads PHP files with extensions .php, .php3, .php4, .php5, .php7, .phtml, and .phar inside your wp-content directory. It skips files larger than 512 KB and enforces a 25-second time budget and a 500-file cap per run to protect shared-hosting environments.
Legitimate image, video, and document uploads are never .php files. If the scanner finds any PHP file inside wp-content/uploads/, it is almost certainly a backdoor uploaded through a vulnerable plugin or theme — a High severity threat that should be removed immediately.
Yes — the malware auto-purge feature lets you delete or quarantine flagged files directly from the scan results screen. Always review the file path and threat type before purging.
No. The plugin makes zero external HTTP requests. All scan results and alert history live only in your WordPress database.
Login protection limits repeated failed login attempts and helps prevent brute-force attacks against your wp-login.php endpoint — a key layer of website security that works alongside the malware scanner.
Go to Malware Cleaner → Scan Results and click the file path to view the matched pattern. The troubleshoot view shows the exact line and rule that triggered the alert, so you can decide whether it is a false positive or a real threat.
Go to Malware Cleaner → Settings, enable Remove all data on uninstall, then deactivate and delete the plugin. All database tables, scan history, and plugin options will be removed automatically.
The scanner caps each run at 500 files and 25 seconds to be safe on resource-constrained servers. If your wp-content directory is very large, only the first 500 PHP files encountered will be inspected per run. Future versions will support paginated / batch scanning.