by
Hanuit Solutions
4.5 (2 reviews)
Hanu Malware Guard
Scans files for malware, tracks file integrity, audits WP-Cron for planted jobs, and blocks login brute-force and common attacks.
Hanu Malware Guard ranks #61,013 among WordPress.org plugins with 1+ active installations, is #2,854 of 5,058 in the Security category, a 4.5/5 rating from 2 reviews, and was last updated Sep 22, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v1.2.8
Current Version v1.2.8
Updated 1 month ago
Last Update on 22 Sep, 2026
Refreshed 1 week ago
Last Refreshed on
#2,854 of 5,058 in Security
Rank
#61,013
—
No change
Active Installs
1+
-66.7%
KW Avg Position
56.5
0.5 better
Downloads
162
+2 today
Support Resolved
0%
—
No change
Rating
90%
Review 4.5 out of 5
4.5
(2 reviews)
Next Milestone 10
0+
10+
48,076
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 7 more installs to reach 10+
Rank Changes
Current
#61,013
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
4.5
2 reviews
Overall
90%
5
1
(50%)
4
1
(50%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.2.8
- Last Updated
- Sep 22, 2026
- Requires WP
- 6.2+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- Hanuit Solutions
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 4.5
- Reviews
- 2
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
LiteSpeed Cache
7M+ installs
#5
Akismet Anti-spam: Spam Protection
5M+ installs
#8
Wordfence Security – Firewall, Malware Scan, and Login Security
5M+ installs
#11
Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)
3M+ installs
#18
Hostinger Tools
3M+ installs
#20
WPS Hide Login
2M+ installs
#27
Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention
1M+ installs
#33
WP Super Cache
1M+ installs
#36
Frequently Asked Questions
Common questions about Hanu Malware Guard
No security scanner can guarantee that, and you should be skeptical of any that claims to. The signature scanner and core-integrity checker produce heuristic matches for you to review — they are a strong starting point, not a certified clean bill of health. Always keep offline backups regardless.
Inspect the snippet shown in Scan Results. Several signatures (obfuscated eval(), create_function(), long base64 blobs) can legitimately appear in caching layers, minified vendor code, or some page builders. If you're confident it's a false positive, click "Ignore" rather than deleting the file. Auto-quarantine of critical findings is off by default for exactly this reason.
Not in real time — no WordPress plugin can intercept a file write at the PHP-engine level; that requires a hosting-level security layer. What it does is control cron scheduling (block a hook so WordPress refuses to re-run it) and detect file changes that happened around the same time as a suspicious cron run, so you can act quickly.
Yes. XML-RPC authentication goes through the same core wp_authenticate() function as the normal login form, so the same failed-attempt counter and lockout apply to both.
The query-string pattern check always exempts logged-in administrators, specifically so normal plugin/editor use can never trigger a self-lockout. Only unauthenticated requests are checked against the SQLi/path-traversal/PHP-injection patterns.
No. The only outbound request the plugin makes is to WordPress.org's own official checksums API, and only your WordPress version + locale are sent (see "External services" above). Everything else — scanning, hashing, cron auditing, login tracking — runs entirely on your own server.
Nothing is left on disk. Quarantining a file reads its content into the database (base64-encoded, in the plugin's own scan_results table) and deletes the original — the file is gone from the filesystem the moment it's quarantined, not just hidden behind a protected folder. Uninstalling the plugin removes that table along with everything else, so if you want to keep a quarantined file's content for forensics, restore or export it before uninstalling.
Use the plugin's support forum on WordPress.org, or email herry@hanuitsolutions.com.
