Follow Me Security

Account takeover prevention that works even after a password leaks

Account takeover (ATO) happens when an attacker signs in to a real user's account. They don't break in; they log in. Follow Me Security makes a correct password useless unless it's typed from a place the real user approved.

How accounts get taken over

  • Reused passwords from other sites' breaches, tried automatically (credential stuffing).
  • Phishing pages that capture the password, and sometimes the 2FA code too.
  • Infostealer malware on a user's computer that sends saved passwords to attackers.
  • Password guessing against weak or common passwords.

In every case, the attacker ends up holding valid credentials. Stolen credentials were the most common initial access vector in the Verizon 2025 DBIR.

Take location away from the attacker

The attacker has the password. What they don't have is your user's network. With Follow Me Security, each login also has to come from the user's current Follow Me IP, their fixed IPs, or your site's allowed IPs. A password used from a botnet, a VPN or another country simply fails, and the user can see the denied attempt in their account.

What it doesn't do (so you can plan around it)

Follow Me Security protects the moment of login. If malware steals a session that's already logged in, or the attacker is on the same network as the user, the IP check can't tell them apart. Keep sessions reasonably short and keep your own 2FA on: the layers work together.

How Follow Me Security works

  1. Your site links up. Install the WordPress plugin, add the PHP drop-in, or use our Node.js or Python package. Any other language can call the API. Users click "Link with Follow Me Security" in their account settings.
  2. Users press Follow Me. From their phone, wherever they are. That network becomes their approved place to sign in.
  3. Every login is checked. After the password is right, your site asks us if the IP is approved. If not, the login is refused, before your own 2FA even runs.

Always an extra layer: passwords and two-factor sign-in still apply. IPs are stored only as keyed one-way hashes.

Frequently asked questions

Will this stop attackers who have the password and 2FA code?

At login, yes, unless they are on an approved network. A phished password and code typed from the attacker's own connection is refused.

Do users see blocked attempts?

Yes. Each user sees recent allowed and denied logins on their account page and in the phone app.

How hard is it to add?

For PHP sites, it's a downloaded folder and two lines of code. Other stacks use a small signed API.

Add a location check to your logins today

$19/month per website or app. Free for every user. Set up in minutes.