susheelhbti

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.
<ul>
<li>Behavior-based blocking — exploit-path probes (<code>.env</code>, <code>wp-config</code> backups, <code>.sql</code> dumps), malicious user agents, and request floods.</li>
<li>Rate limiting — every visitor is rate limited; hits on exploit paths count double, so scanners get banned far faster than real visitors ever could.</li>
<li>Honeypot traps — invisible links only bots follow; one visit means a permanent ban.</li>
<li>Subnet bans — block a whole CIDR range (e.g. <code>20.100.172.0/24</code>) when attackers rotate IPs on cloud providers.</li>
<li>Text attack reports — one-click downloadable <code>.txt</code> reports (summary + raw log) listing every URL attackers tried to access, ready to hand to your hosting company.</li>
<li>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.</li>
<li>Fails open — any internal error and your site keeps working normally. An emergency <code>disable.flag</code> file shuts blocking off instantly via FTP.</li>
</ul>
<h4>Strongest mode (optional)</h4>
By default the firewall runs when plugins load — before WP routing, themes and queries. For maximum resource savings you can point PHP’s <code>auto_prepend_file</code> at <code>firewall.php</code> so blocking happens before WordPress loads at all. See the FAQ.
<h4>Honest limitations</h4>
<ul>
<li>This is a request firewall, not a malware scanner — it will not detect an already-infected site.</li>
<li>It ships with rules for today’s common probes and has no cloud threat feed; review the rules occasionally.</li>
<li>The “Block xmlrpc.php” option breaks Jetpack and the WordPress mobile app — disable that single toggle if you use them.</li>
<li>All assets (CSS/JS) are bundled — the plugin makes no external network requests.</li>
</ul>

TrapFlux Request Firewall

Lightweight, behavior-based bot firewall. Blocks scanners before WordPress loads, with text attack reports for your hosting company.

sourcecode347

The Anti Browser DDoS Protection plugin provides robust protection against denial-of-service (DoS) attacks on your WordPress site. It implements IP-based rate limiting, with configurable settings for subscribers, non-logged-in users, and verified bots, while excluding administrators and other non-subscriber roles. It features advanced bot detection to identify and limit suspicious bots, immediate blocking of malicious bots by User Agent, and supports Cloudflare for accurate client IP detection. Static assets (e.g., CSS, JS, images) are excluded to maintain site performance. An intuitive admin panel allows you to configure rate limits, bot exclusions, trusted bot IP ranges (with automatic duplicate removal), blocked bots by User Agent, log expiration settings, and view logs for blocked IPs, banned IPs, and high traffic bots with auto-refresh every 30 seconds, all with User Agent details and timestamps. You can export Excluded Bots, Bot IP Ranges, and Blocked Bots lists to .txt files and import new entries to append to existing lists without duplicates. Daily bar charts for Blocked IPs, Banned IPs, and High Traffic Bots are displayed above the logs for quick visual insights.
Key Features:
<ul>
<li>Rate limiting based on IP for subscribers and non-logged-in users, with configurable maximum requests and time window.</li>
<li>Excludes non-subscriber logged-in users (e.g., administrators, editors) from rate limiting.</li>
<li>Advanced bot detection to identify suspicious bots (bots using trusted User Agents but from unverified IPs).</li>
<li>Suspicious bots are subject to the same rate limiting as regular users and logged with User Agent in the Blocked IPs Log.</li>
<li>Immediate blocking of malicious bots by User Agent (e.g., MJ12bot, SemrushBot, DotBot by default) with customizable settings and logging.</li>
<li>Configurable rate limiting for verified excluded bots (default: 100 requests per minute), with logging for bots exceeding this limit.</li>
<li>High Traffic Excluded Bots Log to track verified bots with excessive requests, including IP, User Agent, and timestamp.</li>
<li>Admin panel to configure maximum requests, time window, excluded bots, trusted bot IP ranges, blocked bots (User Agents), blocks before ban, ban duration, high traffic bot limits, and log expiration (days).</li>
<li>Export Excluded Bots, Bot IP Ranges, and Blocked Bots lists to .txt files for backup or transfer.</li>
<li>Import .txt files for Excluded Bots, Bot IP Ranges, and Blocked Bots to append new entries to existing lists, with automatic duplicate removal.</li>
<li>Automatic removal of duplicate IP ranges in the Bot IP Ranges field on save, keeping the first occurrence.</li>
<li>Support for Cloudflare real IP detection using <code>CF-Connecting-IP</code> and <code>X-Forwarded-For</code> headers.</li>
<li>Excludes static assets (CSS, JS, images, fonts, etc.) from rate limiting to optimize performance.</li>
<li>Logs blocked IPs, banned IPs, and high traffic bots with IP, User Agent, and timestamps using the WordPress timezone, viewable in the admin panel with options to clear logs and auto-refresh every 30 seconds.</li>
<li>Daily bar charts for Blocked IPs, Banned IPs, and High Traffic Bots displayed above the logs in the admin panel for visual statistics.</li>
<li>Automatic log expiration (Blocked IPs, Banned IPs, High Traffic Bots) after a configurable number of days (default: 5 days), with hourly cleanup via WordPress Scheduler.</li>
<li>All error messages and logs prefixed with “Anti Browser DDoS Protection: ” for clarity.</li>
<li>Donate link in the admin panel to support the project.</li>
<li>Automatic cleanup of transients, blocked IPs, banned IPs, high traffic bots, blocked bots, bot IP ranges, and log expiration settings on plugin deactivation to prevent database bloat.</li>
</ul>
Ideal for WordPress sites seeking enhanced security against automated attacks, with seamless integration for Cloudflare users, advanced bot management, efficient log management, visual charts for statistics, and easy export/import for bot lists.
<h3>Plugin Assets img/</h3>
<h3>Icon Image</h3>
Normal: icon-128×128.png 
High-DPI (Retina): icon-256×256.png
<h3>Bugs</h3>
Caching plugins such as WP Super Cache, W3 Total Cache, and others may bypass the DDoS protection provided by Anti Browser DDoS Protection, serving cached pages without triggering the plugin’s checks for blocked bots, rate limiting, or banned IPs. 
– Solution: Disable all WordPress caching plugins to ensure full DDoS protection. Instead, enable Browser Caching using a service like Cloudflare to improve performance without compromising security. 
 Enable standard type Caching and Configure Cloudflare Browser Cache TTL (e.g., 8 days) via Caching > Configuration in the Cloudflare dashboard.- Cloudflare Compatibility: Ensure Cloudflare is configured to pass <code>CF-Connecting-IP</code> headers for accurate IP detection. Check your Cloudflare dashboard if logged IPs are incorrect. 
– Bot IP Ranges: Update the Bot IP Ranges field every 6 months (next update: March 2026) using official sources (e.g., Google, Bing, Yandex documentation). Duplicate ranges are automatically removed on save. Export to .txt for backup or import from .txt to append new ranges. 
– Blocked Bots: Add malicious bots to the Blocked Bots (User Agents) field (e.g., MJ12bot, SemrushBot, DotBot) to block them immediately. Blocked bots are logged with their IP and User Agent. Export to .txt for backup or import from .txt to append new entries. 
– Excluded Bots: Add trusted bots (e.g., Googlebot, Bingbot) to the Excluded Bots field to exempt them from regular rate limiting (if from verified IPs). Export to .txt for backup or import from .txt to append new entries. 
– High Traffic Bots: Verified bots exceeding the configured limit (default: 100 requests per minute) are logged for monitoring but not blocked. Check the High Traffic Excluded Bots Log regularly. 
– Log Expiration: Set the Log Expires (Days) setting to control how long logs are retained (default: 5 days). Cleanup runs hourly via WordPress Scheduler. Logs older than the specified days are automatically deleted. 
– Timezone: Set the WordPress timezone correctly (e.g., <code>Europe/Athens</code> for Greece) in Settings > General > Timezone to ensure accurate timestamp display in logs and charts. 
– Performance: For high-traffic sites, clear the Blocked IPs Log, Banned IPs Log, and High Traffic Excluded Bots Log regularly, or set a lower Log Expires (Days) value to prevent database growth. 
– Customization: Contact the author for additional features like custom error pages, email notifications for high traffic bots, or advanced logging. 
– Support the Project: If you find this plugin useful, consider supporting its development via the <a href="https://buy.stripe.com/bIY5o70SSfam8Qo7ss" rel="nofollow ugc">donation link</a> in the admin panel or plugin page.

Anti Browser DDoS Protection


I hope it helps Wordpress users protect themselves from DDoS attacks, it also protects you from Javascript Based DDoS Attacks that exploit the Subresource Integrity (SRI) vulnerability, from which neither Crowdsec, nor Mod_Evasive, nor IP_Tables Rules nor Cloudflare protect you.I struggled until I fortified my page and I have all the above services enabled, finally I succeeded by creating this Wordpress Security Plugin.I am very satisfied that I made it available for other users to use completely free of charge, it is open source software with License GPL 2.0.


It also protects you from Javascript Based DDoS Attacks

Protects WordPress from DDoS with rate limiting, bot detection, blocking, Cloudflare support, logs, charts, and bot list export/import.

TrapFlux Request Firewall vs Anti Browser DDoS Protection