I would like to officially introduce BotBlocker Security - a WordPress plugin built to provide an early layer of protection against bots, botnets and automated attacks.
More than 500 companies run BotBlocker on their own infrastructure.
The project grew out of real experience: constant brute-force attempts, vulnerability scanners, fake search robots and overloaded log files. The goal is protection that works before WordPress starts consuming resources.
What BotBlocker focuses on
- early filtering of incoming traffic and lower server load;
- blocking automated attacks;
- transparent monitoring and logging.
Key capabilities
- Early launch. Requests are filtered before WordPress is fully loaded via MU mechanics, which saves CPU and memory and blocks junk traffic as early as possible.
- Firewall / WAF. Incoming requests are analysed, checked for suspicious patterns and blocked by malicious signatures.
- Anti-bot protection. Detection of automated behaviour, botnet filtering and blocking of fake User-Agents.
- Login protection. Admin panel and wp-login.php protection with brute-force attempt control.
- IP analysis. Blacklists, dynamic blocking and IPv4/IPv6 support.
- Monitoring and logging. A security event log, a list of blocked requests and activity analysis.
- Performance. Minimal load in normal mode, lower load during attacks and compatibility with caching and CDN.
How a request gets filtered
BotBlocker loads as an MU-plugin, so its code runs before regular plugins and before the theme. A request that fails the checks is refused there: WordPress does not boot, the database is not queried and the page is not built. On a shared host that matters, because a bot wave otherwise eats the CPU your visitors need.
What BotBlocker Security checks on every request
Eight checks run on every visitor: cookies, IP reputation, request behaviour, anti-detect scoring and a few more. The point is to catch a bot that copied a real browser’s headers, not one that admits what it is in the User-Agent. When the score is unclear, the visitor gets a challenge: one of eight CAPTCHA modes, including image recognition and moving shapes.
Do not stack BotBlocker on top of another WAF at the same level: two filters fight each other and make the logs unreadable. Pick one place for the decision.
The signature part of the firewall runs before that: known malicious patterns are blocked outright. Login pages have their own limits, with brute-force control and two-factor authentication.
Logs and tuning
Every decision shows up in the log: time, address, path, the rule that fired. That is how you tell a bot wave from a broken cache or a monitoring service that hits the site too often. Expect false positives in the first week: search crawlers, uptime checks and payment callbacks are the usual suspects. Add them to the allowlist and keep the log open for a few days.
Load and numbers
On a normal request the plugin adds a few checks before PHP, which costs less than booting a full WordPress stack for a bot. During an attack the load goes down, not up, because blocked traffic never reaches the site. Today BotBlocker has 14,000 installs in WordPress.org and sees around 100,000 attacks a day.
When it is not the answer
The WordPress plugin security handbook and the OWASP Top 10 cover the code side that no firewall can fix. If the site has no traffic worth protecting and no login attempts, a small plugin for logins and two-factor authentication is enough. BotBlocker is built for sites that see bots every day, or for those where one flood has already taken the site down.
First week after install
Add the search crawlers and uptime checks you trust to the allowlist before the first bot wave arrives. Open the log daily and look for blocked requests that should have passed: checkout callbacks, payment webhooks, the monitoring service. Turn on two-factor authentication for every administrator. Keep a copy of the allowlist outside the plugin in case you reinstall it.
Thank you to everyone who tests, suggests ideas and helps improve BotBlocker. This is a young product, and feedback shapes it more than any roadmap.
Related reading: The best WordPress security plugin: what actually matters and BotBlocker vs Cloudflare: why a generic shield fails WordPress.