Witen Blocker – Security, Firewall, Login Protection & AI Crawler Blocking

By witenlabs

0+ active installationsVersion 0.6.57

Security firewall for WordPress: block attackers and bad bots, limit login attempts, add 2FA, scan for malware, and choose which AI crawlers get in.

Description

Witen Blocker is a security firewall for WordPress. It blocks attackers and known exploits, locks out bots guessing your password, adds two-factor sign-in, scans your files for malware, stops comment spam, and lets you choose which AI crawlers can read your content. Protection starts the moment you activate it, with no account and no setup wizard.

Lock out password guessers

By default, five failed sign-ins from one address in five minutes trigger a one-hour lockout. You can change all three limits under Witen > Login. Slow guessing is caught too: twenty failures within an hour lock the address out for a day. Add two-factor sign-in with any authenticator app and printable recovery codes, so a stolen password alone no longer opens your dashboard. Move the login page to an address only you know. Witen keeps your login names from visitors who ask your site for them, and the sign-in screen never says whether a name is a real account.

Block known WordPress exploits

Template traversal and comment exploit requests are refused before they reach the vulnerable WordPress code. No account needed.

Choose which AI crawlers read your site

Every recognized crawler gets its own allow or block switch. Welcome every AI crawler, block them all, or pick one by one. Nothing is blocked until you choose.

Witen Blocker recognizes GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, PerplexityBot, Common Crawl, Meta-ExternalAgent, Amazonbot, and Applebot, plus the major search engines and ten uptime monitors, so you can configure them separately.

robots.txt states your preference; Witen Blocker enforces it. A crawler you block gets an HTTP 403. Crawlers are matched by their published network ranges as well as their user agent, so a scraper pretending to be Googlebot doesn’t get Googlebot’s pass.

Stop comment spam without a spam service

A hidden field and a timing check catch bots, and a comment that is nothing but one link between two colons goes to the Spam folder (comments from moderators and administrators are not affected). No comment text ever leaves your site.

Connected sites can also use a separate shared spammer list for comments. Repeated honeypot detections from different sensors and customer licenses can contribute addresses to this list. Timing checks and hits on the shared list do not contribute new shared reputation. Review flagged comments under Comments > Spam. If signup protection is enabled, the shared list also filters registrations. To turn off the list, open Witen > Settings.

Catch unexpected file changes

A daily scan checks WordPress core against the official checksums, flags new and changed files, and looks for known malware patterns. Nothing is deleted or changed without you. Connected sites also receive maintained malware catalogs.

Block attackers before they reach you

Connect a free Witen account to download a blocklist based on reports from participating sites and servers. WordPress checks requests against its local copy.

Connecting requires a Witen account and security-event sharing. Every local feature stays free, with no trial expiry. Free connected sites refresh daily and receive up to 50 addresses with a 14-day eligibility delay. Paid plans add more sites and servers, other feed profiles, and off-site backup storage.

Shared hosting or your own server

On shared hosting, WordPress enforces lockouts itself. On a Linux server, you can connect the plugin to Witen Warden for firewall enforcement when the server sees the visitor’s IP address. Behind a CDN or trusted reverse proxy, the plugin enforces login lockouts in WordPress. To review them, open Witen > Firewall.

Get started: activate Witen Blocker and open Witen > Dashboard to see what’s already on. Use Firewall > Bots and AI crawlers to choose which crawlers can visit, and Login to set up two-factor sign-in.

Setup guide | Witen plans | Support

External Services

Witen Collector

Connected features use https://collector.witenlabs.com. Enrollment exchanges your setup token and installation identity for a credential. Witen processes shared reports to identify distributed attacks and provide threat intelligence.

Background sync sends events and site details (listed below) and retrieves blocklists, bot identities, signed malware catalogs, Tor exit nodes, allowlists, service status, network statistics, and feed profiles. Profile changes send your selection and site identifier; IP lookups send the queried address. Block reports include the IP, rule, outcome, request context, and site identifier.

  • Malware samples: off by default. Setting WITEN_SEND_MALWARE_SAMPLES to boolean true in wp-config.php permits file-content uploads. Scans do not require them.
  • Plugin and theme versions: off by default. Enabling vulnerability alerts sends each installed plugin and theme folder name, version, and active state, which Witen matches against known vulnerabilities. Turning the setting off deletes the list Witen holds. On sites connected through Warden, Warden sends the list, with the WordPress and PHP versions, only when package listing is also turned on for the server.
  • Off-site .htaccess backups: off by default. Enabling them permits encrypted file uploads, with checksum and size, and dashboard-requested restores. Witen can decrypt the files and keeps 10 versions. Your site writes a restore only when it matches one of the last 10 backups it uploaded, keeps a local backup, puts the previous file back if your site stops loading, and reports the result. Disabling the option stops uploads and remote restores; local backups remain available.

Witen terms | Witen privacy policy

WITEN_COLLECTOR_URL selects another collector if you operate one; its operator's policies apply. Explicitly configuring `WITEN_SOCKET_PATH` authorizes sharing with local Warden, whose configuration controls onward delivery. Detecting a socket alone does not enable sharing.

Cloudflare proxy ranges

Enrolled sites refresh https://www.cloudflare.com/ips-v4/ and https://www.cloudflare.com/ips-v6/ during background maintenance to recognize trusted proxies. Offline sites use bundled ranges. Requests send ordinary HTTPS network metadata, not WordPress visitor events or account data.

Cloudflare terms | Cloudflare privacy policy

WordPress.org core checksums

Integrity scans request official hashes from https://api.wordpress.org/core/checksums/1.0/, sending your WordPress version, locale, and ordinary HTTPS network metadata. No visitor events, account data, or site content is sent.

WordPress.org privacy policy

The plugin does not remotely load executable code or frontend assets. Bundled bot references cause no remote requests or crawler DNS lookups. Collector connections use your DNS resolver. Background jobs and Apache rule checks call your own WordPress URLs.

Privacy Policy

Events stay local until enrollment or explicit Warden socket configuration. Earlier events are never uploaded retroactively. Connected intelligence requires event sharing. Deactivate the plugin to stop reporting from WordPress; a separately running Warden keeps its own reporting configuration.

What is shared: IP addresses; successful and failed logins; XML-RPC, comment, registration, and 404 events; request URLs, methods, User-Agent strings, referrers, and query information. A username is shared in two cases only: when an account signs in, and when an account’s password was correct but its two-factor code was not. The name typed in a failed sign-in is not shared, and neither is a commenter’s name. Installation reports include site name and URL, WordPress/PHP/plugin versions, and a random installation identifier. An observed IP is not necessarily an attacker. Reports help identify distributed attacks, relate failed logins to later successful ones, and maintain blocklists.

Event reports exclude form bodies, post content, comment text, password fields, cookies, and session data. URLs and metadata can contain personal data. File samples and .htaccess backups are separate options, described above. WITEN_NO_TELEMETRY stops daily installation reports, but not connected security-event sharing.

Local storage: the delivery queue holds up to 500 events for seven days. Witen also keeps the latest 100 dashboard events and blocks, block and allow lists, and health counters. Rejected events and block-decision reports have separate diagnostic queues, each limited to 100 records or 1 MiB. Older records are removed at the limit; diagnostics otherwise remain until uninstall.

Deactivation preserves settings and existing .htaccess and Warden firewall rules. Uninstall removes Witen options, transients, scheduled actions, and database tables. Collector retention follows its operator’s privacy policy; request collector-side deletion from that operator.

Installation

  1. Open Plugins > Add New Plugin, search for Witen Blocker, and install and activate it. You can also upload the plugin ZIP.
  2. Open Witen > Firewall and add your own IP address to the never-block list. Then choose which bots and AI crawlers to allow.
  3. Open Witen > Login to set up two-factor sign-in for your account.
  4. Optional: to add shared blocklists, create a Witen account, add your WordPress site from the dashboard, and enter its one-time setup token in Witen > Settings. Review the terms and privacy information before connecting. The first blocklist arrives after background maintenance runs.

See the setup guide to connect a local Warden agent or configure your site through wp-config.php.

FAQ

How is this different from robots.txt?

robots.txt states your preference, and crawlers that honor it follow it. Witen Blocker enforces your choice: a crawler you block gets an HTTP 403, and a crawler you allow passes. Use both if you like.

What can I use without an account?

Everything local: AI crawler and bot controls, login lockout, two-factor sign-in, comment spam checks, exploit blocks, file and malware scans, and the .htaccess editor. A Witen account adds shared blocklists and reporting.

Will it slow down my site?

Request checks use local data. Blocklist updates, reporting, and scans run in background jobs.

Can I use it alongside another security plugin?

Yes. If both plugins handle two-factor, login limits, bot rules, or .htaccess, turn each feature on in one plugin only, then test your login.

How do I change login limits or recover from a lockout?

Open Witen > Login > Login lockout to set the failure window, failure count, and ban duration. Defaults are 5 failures in 5 minutes and a 1-hour ban. A second limit catches slow guessing: 20 failures within an hour lock the address out for a day (WITEN_LOGIN_SLOW_MAX_FAILURES in wp-config.php changes it; 0 turns it off). Saved settings override WITEN_LOGIN_WINDOW_SEC, WITEN_LOGIN_MAX_FAILURES, and WITEN_LOGIN_BAN_SEC in wp-config.php. Every failure from an address counts toward its ban. Signing in clears only the failures against your own account and never lifts a ban.

Keep your 2FA recovery codes. Authenticator secrets are encrypted with the security keys in wp-config.php, so if you change those keys, sign in with a recovery code and set two-factor up again. If you lock yourself out, wait for the ban to expire or follow the recovery guide, which covers WP-CLI and SFTP. Deactivating the plugin leaves existing .htaccess and Warden firewall rules in place; the guide shows how to remove them.

Can visitors find out my login name?

Witen restricts anonymous author lookups by user ID and through the REST API. The sign-in and password-reset screens give the same response whether or not the account exists. One place remains by design: WordPress author pages display an author slug, which can match the login name. If your site does not need author pages, turn on “Also hide author pages” under Witen > Settings > Advanced. If it does, turn on two-factor for those accounts and set a display name that is not the login name.

Does a scan finding mean my site is hacked?

No. A finding is a file worth a look, and legitimate customizations can trigger one. Witen Blocker shows you which files to check. It doesn’t clean an infected site for you.

What happens if Witen is unavailable?

Your site stays protected. Local protection keeps running, cached blocklists stay in use until they expire, and reports queue and retry in the background. Sites that report through a local Warden agent wait for Warden rather than reporting to Witen directly.

Does it support multisite?

Yes. Each site has its own settings, connection, logs, and jobs. The main site’s network administrator controls the shared .htaccess, and user accounts and two-factor setup are network-wide. If you use a local Warden agent, connect each site separately.

Screenshots

Changelog

0.6.57

  • REST comments can quote literal shortcode escapes. When a batch exceeds the pingback limit, the activity log records which method was limited.

  • Comments containing only a link between two colons go to Spam. Moderators can restore them from the Spam folder. The check runs on your site and exempts comments by moderators and administrators.

  • Protection for three WordPress 7.1.5 flaws, until you update. Template Part blocks crafted to hijack the block editor are refused in comments and post saves. Comments that hide HTML behind escape codes in a shortcode go to Spam, where you can restore a real one. One XML-RPC request now gets one pingback, not an unlimited batch of outbound fetches. Update WordPress anyway: this covers the attacks that need no account, not all twenty fixes.

0.6.56

What you will notice after upgrading

  • A renamed login page stays hidden. Visiting /wp-admin/ without being signed in now answers “not found” instead of sending you to your login address, and so do /login, /admin, and /dashboard. Bookmark your login address. Adding ?witen_login=1 to your home page no longer opens the login.
  • Your login names are kept from visitors. Asking your site for a user by number (yoursite/?author=1) or through the REST API now answers “not found” to anyone who is not signed in. The sign-in screen says “The username or password is incorrect” whether the name or the password was wrong, and the password-reset screen says “check your email” for any name, so a mistyped username there shows no error. Author pages stay unless you turn on “Also hide author pages” under Settings, Advanced.
  • New screens. An activity log, linked from the dashboard, shows the blocks, sign-ins, scans, and setting changes Witen recorded, keeps 90 days, and can be emptied. The Firewall page lists the lockouts your site is holding, each with a Lift link.
  • Signup spam is refused before the account exists, on by default, on the WordPress registration screen, multisite signup, and the WooCommerce account form. You choose how strict usernames are.
  • Two-factor after a key change. If you change the security keys in wp-config.php, the sign-in screen now says authenticator codes need setting up again and asks for a recovery code, and administrators see a notice.
  • Connected tools. With WordPress 6.9 or later, tools you connect as an administrator can read your protection status. They can change blocking only after you turn that on under Settings, Advanced.

Lockouts

  • Slow password guessing is locked out. Trying one password every few minutes used to stay under the limit forever. Now 20 failed sign-ins from one address within an hour lock it out for a day. Someone who mistypes and then signs in stops counting, so people sharing an office address are not locked out by each other’s typos. Failed application-password sign-ins now count too.
  • Broken images, scripts, and links on your own pages no longer lock your visitors out, and one wrong password can no longer lock someone out during an attack on your login.
  • IPv6 lockouts cover the visitor’s whole /64 network, so changing address no longer escapes them.
  • With Warden on the server, lockouts always happen, including for visitors behind a CDN, and Warden decides when they end: with Warden 0.1.48 or later, “sudo warden unban” ends the site’s own lockout too, within about a minute.
  • Unblocking an address from the Witen feed now lasts, and Witen refuses to block a CDN address your visitors share, your own connection, or an address you recently signed in from.

Your server files and your data

  • The blocklist rules Witen writes to .htaccess can no longer open up a password-protected site, every .htaccess change is checked and undone if your site stops loading, and an off-site restore is written only when it matches a backup your own site uploaded.
  • Witen no longer writes to the database on every page view of a site that is not connected, and connected sites no longer look up Witen’s address while serving a visitor.
  • Commenter names are no longer sent to Witen, a mistyped username on a failed sign-in is no longer stored, and deleting the plugin removes everything it stored.
  • A paid site keeps its plan when Witen cannot be reached.

Every change is listed in changelog.txt in the download.

0.6.55

  • Malware scans keep going when a folder or file can’t be read, and keep every match they found. Before, one unreadable folder could stop the scan and lose its results.
  • The Security Scan page lists the paths it couldn’t check as scan warnings, apart from malware results. Warnings are never sent as malware samples.
  • You can turn off Witen’s comment spam protection in Settings, for example if Akismet or another plugin already filters your comments. It stays on by default. Turning it off removes the hidden comment-form fields and timing check, and stops the shared spammer list.
  • Bundle Witen SDK 1.8.2.

0.6.54

  • The server rules page no longer gives your site a letter grade, on purpose. The grade rewarded rules that switch features off, such as blocking XML-RPC, which breaks Jetpack and the WordPress mobile apps, and it dropped whenever we added a rule. It now shows how many recommended rules are on.
  • Recommended rules have no real downside for a normal site. “Turn on recommended rules” replaces “Enable All” and never turns on an optional rule.
  • Blocking XML-RPC and hiding the server signature are now optional rules, listed apart with what each one turns off. If you already block XML-RPC, it stays blocked. Most sites can leave XML-RPC on: login lockout already covers it, and WordPress checks only one password per XML-RPC request.
  • New recommended rule: block the upgrade folder. WordPress 7.1.4 fixed an attack on wp-content/upgrade during updates; this rule refuses every web request into that folder. A one-time notice on Witen pages offers to turn it on.
  • When your server lets WordPress load its own pages, every change to .htaccess now checks, past any cache, that your site still loads, and puts the file back if it does not. Where the check cannot run, Witen says so and tells you how to undo the change. On a host that does not allow a rule, the other recommended rules still turn on, and Witen names the one it left off.
  • Changes that fail now say why, instead of reporting success.
  • With Warden on the server, the login lockout settings now show the lockout Warden really enforces. If Warden allows a shorter lockout than the one you set, or counts failed sign-ins across your sites and locks an address out before your limit, the settings say so. Warden 0.1.41 enforces the lockout length you set, up to one day by default; older versions cut it to an hour, and the settings warn when that applies.
  • Treat requests for PHP files inside wp-content/upgrade as webshell probes.
  • Bundle Witen SDK 1.8.1.

0.6.53

  • Turn on Vulnerability alerts in Settings to share your installed plugin and theme versions. Witen then lists the ones with known vulnerabilities, and the version that fixes each, on the Vulnerabilities page of your Witen dashboard. It is off until you turn it on, and only plugin and theme names and versions are sent.
  • Turning Vulnerability alerts off deletes the shared list from Witen.
  • Sites connected through a local Warden share the list through Warden 0.1.35 or later, only when package listing is turned on for the server too.
  • Bundle Witen SDK 1.8.

0.6.52

  • Check comments on connected sites against a separate shared spammer list. An address joins it only after honeypot detections from different customer licenses and sensors. Matching comments go to the Spam folder for review and never block pages or logins. Turn it off in Settings.
  • Report why a stored comment was marked as spam: honeypot, timing, or the shared list. Comment text and email addresses are never sent.
  • Never ban an unlisted reverse proxy on a private network. Failed logins through it are still recorded and counted. Trusted proxies now says plainly when a public address that sends forwarding headers can be banned.
  • Record a correct password still waiting for its two-factor code in the audit log. It never counts as a failed login, never resets the failure count, and never lifts a ban.
  • Count each failed login against the account it tried. Signing in clears only that account’s failures, so a valid password for one account cannot reset the count against another. Failed logins recorded before the update keep counting.
  • With a local Warden, show which blocks live in the server firewall. WordPress cannot lift those, so the blocklist no longer offers Unblock for them, and a new note gives the exact server command for each kind of block.
  • Never ask a local Warden to lock out an allowlisted address after failed logins.
  • Bundle Witen SDK 1.7.

See changelog.txt in the download for older releases.