Patrick Schlesinger

ReportedIP Hive Light protects WordPress logins against brute-force and password-spray attacks. It is intentionally focused: a per-IP attempt counter, a progressive block ladder, and an optional community lookup. No bloat, no dashboards, no upsell.
Two operating modes
<ul>
<li>Local Shield (default). Counts failed logins per IP and blocks attackers based on configurable thresholds. The plugin makes zero outbound network requests in this mode — all data stays on your server.</li>
<li>Community Network (optional). When you enter a free Community Access Key from reportedip.de, the plugin additionally checks the source IP against the reportedip.de community database during login attempts and shares blocked IPs back to the community. Both calls are clearly disclosed in the settings UI.</li>
</ul>
How it works
<ul>
<li><code>wp_login_failed</code> increments a per-IP counter using an atomic upsert (no race conditions under concurrent attacks).</li>
<li>When the counter exceeds your threshold, the IP is blocked for a duration drawn from a progressive ladder (5 min → 15 min → 30 min → 24 h → 48 h → 7 days).</li>
<li><code>wp_authenticate_user</code> short-circuits known-bad IPs before the WordPress core authentication runs.</li>
<li>Cache plugins (WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed) are honoured via the HTTP 403 status plus explicit <code>Cache-Control: no-store, no-cache, must-revalidate, max-age=0</code> and <code>Pragma: no-cache</code> headers on the block page.</li>
</ul>
Privacy
<ul>
<li>IP addresses are processed for the legitimate purpose of network security (GDPR Art. 6(1)(f)).</li>
<li>Usernames are stored only as a SHA-256 hash, salted with <code>wp_salt()</code>. Plain-text usernames are never persisted or transmitted.</li>
<li>In Local Shield mode, no data leaves your server. In Community Network mode, only the IP, hashed username, event type, and timestamp are sent — no domain, no contact details, no traffic data.</li>
</ul>
For developers
<ul>
<li>Filters: <code>reportedip_hive_is_whitelisted</code>, <code>reportedip_hive_get_client_ip</code>, <code>reportedip_hive_event_category_map</code>, <code>reportedip_hive_api_endpoint</code>.</li>
<li>Actions: <code>reportedip_hive_log</code>, <code>reportedip_hive_ip_blocked</code>, <code>reportedip_hive_report_queued</code>.</li>
</ul>
A free Community Access Key is available at reportedip.de. The plugin works without one in Local Shield mode.
<h3>External services</h3>
This plugin can connect to the ReportedIP API at <code>https://reportedip.de</code>. All 
external requests are opt-in only — they are made exclusively when (a) a 
“Community Access Key” has been entered in the plugin settings and (b) the 
“Operation Mode” is set to “Community Network”. The default mode is “Local 
Shield”, which performs zero external requests.
<h4>Endpoint 1: IP-reputation lookup</h4>
<ul>
<li>URL: <code>https://reportedip.de/wp-json/reportedip/v2/check?ip={ip}</code></li>
<li>HTTP verb: GET</li>
<li>Auth header: <code>X-Key: {your-access-key}</code></li>
<li>Trigger: a login attempt reaches <code>wp_authenticate_user</code></li>
<li>Timeout: 2 seconds (fail-open — login proceeds when the API does not respond)</li>
<li>Data sent: only the source IP address of the current login attempt</li>
<li>Data NOT sent: usernames, passwords, cookies, server identifiers, domain name</li>
</ul>
<h4>Endpoint 2: Blocked-IP report</h4>
<ul>
<li>URL: <code>https://reportedip.de/wp-json/reportedip/v2/report</code></li>
<li>HTTP verb: POST (JSON body)</li>
<li>Auth header: <code>X-Key: {your-access-key}</code></li>
<li>Trigger: a brute-force / spray threshold has been exceeded; the report is 
queued in the database and dispatched by a 15-minute cron job</li>
<li>Data sent: the offending IP, an integer category ID for the threat type, 
and a short human-readable comment (e.g. “5 failed logins in 15 minutes”)</li>
<li>Data NOT sent: usernames in plain text, passwords, full request bodies, 
domain name, contact information</li>
</ul>
<h4>Endpoint 3: Access-key verification</h4>
<ul>
<li>URL: <code>https://reportedip.de/wp-json/reportedip/v2/verify-key</code></li>
<li>HTTP verb: GET</li>
<li>Auth header: <code>X-Key: {entered-key}</code></li>
<li>Trigger: an administrator clicks “Test connection” in the plugin settings</li>
<li>Data sent: only the access key under verification</li>
</ul>
<h4>Hashing of submitted usernames</h4>
When a brute-force attempt is detected and the failing username is recorded 
locally, the plugin stores <code>sha256( username + wp_salt() )</code> only — never the 
plain text. The salted hash is also what would be transmitted with a report, 
preventing recipients from recovering the original username.
<h4>Service provider</h4>
<ul>
<li>Operator: Patrick Schlesinger, Germany</li>
<li>Service URL: <a href="https://reportedip.de" rel="nofollow ugc">reportedip.de</a></li>
<li>Legal notice (Impressum): <a href="https://reportedip.de/impressum/" rel="nofollow ugc">reportedip.de/impressum</a></li>
<li>Terms of use: <a href="https://reportedip.de/nutzungsbedingungen/" rel="nofollow ugc">reportedip.de/nutzungsbedingungen</a></li>
<li>Privacy policy: <a href="https://reportedip.de/datenschutzerklaerung/" rel="nofollow ugc">reportedip.de/datenschutzerklaerung</a></li>
<li>Source code: <a href="https://github.com/reportedip/reportedip-hive-light" rel="nofollow ugc">github.com/reportedip/reportedip-hive-light</a></li>
<li>Contact: <a href="mailto:1@reportedip.de" rel="nofollow ugc">1@reportedip.de</a></li>
</ul>
You can switch back to Local Shield mode at any time in Settings → ReportedIP 
Hive → Connection. Doing so stops all external traffic immediately.
<h3>Bundled assets</h3>
This plugin ships every stylesheet and script it needs inside the plugin 
folder. No CDN, no Google Fonts, no remote stylesheets, no remote scripts 
are loaded — every asset URL begins with the plugin’s own 
 wp-content/plugins/reportedip-hive/ path.
The full list of bundled, locally-served assets:
<ul>
<li><code>assets/css/design-system.css</code> — design tokens and components used on 
every plugin admin page.</li>
<li><code>assets/css/admin.css</code> — admin-page overrides on top of the design 
system.</li>
<li><code>assets/css/wizard.css</code> — standalone styles for the first-run setup 
wizard.</li>
<li><code>assets/js/admin.js</code> — handles tab switching and the AJAX 
“Test connection” button. Its only network call is <code>fetch()</code> against 
WordPress’ own <code>admin-ajax.php</code> (same origin); no third-party endpoint 
is contacted.</li>
<li>Inline SVG icons (the shield logo, the menu icon, and trust-badge 
glyphs) are emitted from PHP via <code>wp_kses()</code> with an explicit allow-list 
— no <code><img></code> element points at an external host.</li>
</ul>
The complete list of files distributed in the WordPress.org ZIP is 
visible at Plugins → Plugin File Editor once the plugin is installed.
<h3>Third-party services and licences</h3>
<ul>
<li>GPLv2 (or later) licence text is bundled with the plugin in the 
 LICENSE file at the plugin root and is also referenced from the 
plugin header (<code>License URI: https://www.gnu.org/licenses/gpl-2.0.html</code>).</li>
<li>No third-party PHP, JavaScript, or CSS libraries are bundled with 
the plugin. There is no Composer <code>vendor/</code> directory, no jQuery copy, 
no minified third-party bundle. WordPress itself supplies any global 
scripts (<code>jquery</code>, <code>wp-list-table</code>, etc.) and the plugin only depends 
on WordPress core APIs.</li>
<li>The only external HTTP service the plugin can talk to is the 
 https://reportedip.de/wp-json/reportedip/v2/ API, and only when the 
administrator has explicitly enabled Community Network mode — see 
the “External services” section above for the full data flow.</li>
</ul>
<h3>Privacy</h3>
<ul>
<li>IP addresses are processed under GDPR Art. 6(1)(f) (legitimate interest in network security).</li>
<li>Usernames are stored as a salted SHA-256 hash; plain-text values are never persisted or transmitted.</li>
<li>In Local Shield mode (default) no data leaves your server.</li>
<li>In Community Network mode the data listed above is sent to reportedip.de.</li>
<li>Data retention is configurable in Settings → Privacy. The default attempt window is 15 minutes; the API queue retention is 7 days.</li>
<li>Activate “Delete all data on uninstall” in Settings → Privacy to remove all plugin tables and options when the plugin is deleted.</li>
</ul>
<h3>Disclaimer</h3>
ReportedIP Hive Light is provided “as is”, without warranty of any kind, express or 
implied, including but not limited to warranties of merchantability, fitness 
for a particular purpose, and non-infringement. The author shall not be liable 
for any claim, damages, or other liability arising from the use of this 
software (this is the standard GPLv2-or-later disclaimer; see the LICENSE 
file for the full text).
The plugin provides defense-in-depth against brute-force and password-spray 
login attacks. It does not replace strong passwords, two-factor 
authentication, server-level firewalls, or web-application firewalls. No 
single security measure offers a 100 % guarantee against compromise. You 
remain responsible for the overall security posture of your WordPress site.
The optional Community Network mode forwards data to the third-party service 
operated at https://reportedip.de — see the “External services” section 
above for the full data flow. Site operators that enable Community Network 
mode are responsible for assessing the lawful basis under their applicable 
data-protection regime (in the EU, GDPR Art. 6(1)(f) — legitimate interest 
in network security — typically applies) and for updating their own privacy 
policy accordingly.

ReportedIP Hive Light

Lightweight brute-force login protection with optional community-powered IP reputation checks.

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.

ReportedIP Hive Light vs Anti Browser DDoS Protection