Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org
Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →
WP PlugIndex currently records TrapFlux Request Firewall version 1.0.5 as active, updated 4mo ago and tested up to WordPress 7.0.
Overview
About this plugin
TrapFlux Request Firewall is a lightweight request firewall that blocks vulnerability scanners and bot floods by how they behave, not just where they come from.
Behavior-based blocking — exploit-path probes (.env, wp-config backups,.sql dumps), malicious user agents, and request floods.
Rate limiting — every visitor is rate limited; hits on exploit paths count double, so scanners get banned far faster than real visitors ever could.
Honeypot traps — invisible links only bots follow; one visit means a permanent ban.
Subnet bans — block a whole CIDR range (e.g. 20.100.172.0/24 ) when attackers rotate IPs on cloud providers.
Text attack reports — one-click downloadable.txt reports (summary + raw log) listing every URL attackers tried to access, ready to hand to your hosting company.
fail2ban-friendly log — one pipe-delimited line per blocked request, so your host can ban attackers at the network level using the plugin’s detections.
Fails open — any internal error and your site keeps working normally. An emergency disable.flag file shuts blocking off instantly via FTP.
Strongest mode (optional)
By default the firewall runs when plugins load — before WP routing, themes and queries. php so blocking happens before WordPress loads at all. See the FAQ.
Honest limitations
This is a request firewall, not a malware scanner — it will not detect an already-infected site.
It ships with rules for today’s common probes and has no cloud threat feed; review the rules occasionally.
The “Block xmlrpc.php” option breaks Jetpack and the WordPress mobile app — disable that single toggle if you use them.
All assets (CSS/JS) are bundled — the plugin makes no external network requests.
WordPress.org metadata
Plugin tags
Topics listed for this plugin in the WordPress.org directory.
bot blocking
rate limiting
firewall
honeypot
security
Compatibility & maintenance
Compatibility & maintenance
Tested up to WordPress 7.0
Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 7.0.
Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.0
Minimum requirementsWordPress 5.8 · PHP 7.2
Update activity18 Jun 20264mo ago
“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.
Changes recorded by WP PlugIndex
Recent tracked changes
No tracked version or compatibility changes have been recorded by WP PlugIndex yet.
Tracking & source
WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.
