WordPress plugin intelligence profile

Phantom User Lockout

Records logins that use usernames which don't exist (username, password tried, IP, location, host) and blocks the IP until you unblock it.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.2.0
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.2 · PHP 7.2
Directory statusactive
Last directory update29 Sept 20261mo ago
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 Phantom User Lockout version 1.2.0 as active, updated 1mo ago and tested up to WordPress 7.1.

Overview

About this plugin

Bots guess usernames like “admin” and “administrator”. On most sites those names don’t exist, so any attempt with them is a bot. Phantom User Lockout records each one and blocks the IP address that made it.

For every attempt with a username that doesn’t exist on your site, you get:

  • The time, in site time with UTC on hover
  • The username and the password that was tried
  • The IP address, shown as IP Blocked, Not blocked or Safe
  • Where the IP is: city, region and country
  • Who owns it: the hosting company or network (for example “AS53667 FranTech Solutions”) and the reverse hostname
  • How the attempt came in: the login form, XML-RPC (every guess inside a system.multicall batch gets its own row), REST API application passwords, or another login form
  • The user agent and the requested URL

Blocking

  • An IP is blocked after its first attempt with a username that doesn’t exist. You can raise that threshold.
  • Blocks are permanent. They only lift when you press Unblock.
  • A blocked visitor gets a 403 page that reads “IP Blocked”.
  • By default a block covers the login page, XML-RPC, REST logins and any other form that logs in through WordPress. You can widen it to the whole site.
  • Optionally, the plugin can also block IPs that enter the wrong password for a real username. This is off by default, and the default threshold is 3 wrong passwords.

Built not to lock you out

  • Real accounts are never recorded unless you turn on the real-account option, and even then their passwords are never stored.
  • If a username is within two letters of a real login or email, it’s treated as a typo by one of your own people. It’s logged with the password hidden and never causes a block.
  • Safe IPs are never recorded or blocked. Add yours with one click: “Add my current IP address to the list”.
  • A signed-in administrator is never blocked. Neither are the server’s own address and loopback.
  • Emergency switch: add define( 'BOTLO_DISABLE', true ); to wp-config.php.

htaccess or any other server file.

External services

io.

  • What is sent: only the IP address that made the login attempt, plus your ipinfo.io token if you entered one in Settings. No information about your site, your users or your visitors is sent.
  • When: once per new IP address, in the background shortly after its first attempt, or when an administrator opens the Phantom User Lockout screen while a lookup is still pending.
  • Turning it off: Settings → Location lookups.
  • ipinfo.io terms of service: https://ipinfo.io/terms-of-service
  • ipinfo.io privacy policy: https://ipinfo.io/privacy-policy

Privacy

The plugin stores IP addresses, user agents, usernames and passwords from failed login attempts that used usernames which don’t exist. It adds suggested wording to Settings → Privacy → Policy Guide.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • block ip
  • brute force
  • honeypot
  • login
  • security
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.2 · PHP 7.2
Update activity29 Sept 20261mo 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.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.