Use cases

Account takeover prevention: stop takeover bots at login

Stop account-takeover infrastructure at the login form, your auth API, or the CDN edge. Real users and trusted password-manager / AI-agent sessions sign in invisibly; takeover infrastructure is blocked.

How to prevent account takeover: the short answer

Account takeover, usually shortened to ATO, is when someone other than the owner gets into an online account and uses it as if they were the owner. The break-in is the takeover, and ATO fraud is what follows: a saved card spent, a balance moved, loyalty points redeemed or the account itself sold. The FBI's Internet Crime Complaint Center issued a public service announcement on 25 November 2025 saying it had received "more than 5,100 complaints reporting ATO fraud, with losses exceeding $262 million" since January 2025, from one scheme in which criminals pose as bank support staff.

Most account takeover is automated. Attackers take usernames and passwords leaked from other sites and replay them against your login form and auth API, millions at a time, to find the few that work. To prevent it, check every request to login, password reset and account recovery for signs of automation, and stop it before a password is checked. Real users, password managers and trusted AI agents should pass without seeing a challenge.

Multi-factor authentication still matters for the attacks a bot check cannot see, such as a person handing their password to a phishing page. Bot protection removes the scale that makes account takeover worth an attacker's time.

Five routes into an account

1. Credential stuffing. Bots replay username and password pairs leaked in other sites' breaches against your login, counting on people reusing passwords. It is the route that produces takeovers in bulk: Roku disclosed about 576,000 accounts taken this way in a single incident in 2024. The full explanation is in what is credential stuffing. Password spraying, which tries a few common passwords against many accounts, is its close relative.

2. Phishing. The customer is tricked into typing their login details into a fake page. The FBI notice above describes criminals contacting victims by text, call or email, claiming fraud on the account, and sending them to a phishing site or a fake login page bought as a search ad, where they are tricked into giving away "their login credentials, including multi-factor authentication (MFA) code or One-Time Passcode (OTP)". A one-time code read out or typed into the attacker's page is as good as the real thing for the few minutes it lasts.

3. SIM swap. The attacker persuades the victim's mobile carrier to move their number to a SIM the attacker holds, then receives every SMS code sent to that number. In the US, the FCC adopted rules in November 2023 requiring carriers to authenticate customers before a SIM change or port-out and to notify them when one is requested.

4. Session or cookie theft. Once someone has logged in, the site trusts a session cookie rather than asking for the password again. Malware on the victim's computer that copies that cookie lets the attacker skip the login, and the MFA check with it, until the session expires.

5. Password reset and account recovery abuse. Reset and recovery flows often accept less proof than the login: access to the email inbox, a code by SMS, or answers to security questions. An attacker who controls the inbox or the phone number, or who can guess the answers, resets the password and takes the account. Bots also hammer reset endpoints to find which email addresses have accounts.

Which routes into an account bot protection closes

Route inAutomated?What stops it
Credential stuffing with breached passwordsYes, at scaleBot protection on login and the auth API
Password spraying and account-checker toolsYesBot protection, plus rate limits by account and device
Password-reset and account-recovery abuseUsuallyBot protection on reset and recovery, not only on login
Phishing a password and one-time codeNo, one person at a timePhishing-resistant MFA such as passkeys
SIM swap or stolen session cookieNoCarrier controls, session binding, checks after login

The first three are where account takeover happens in bulk, and all three are automated.

What attackers do after a takeover

Spend stored payment methods. In the Roku incident, attackers used saved payment methods in fewer than 400 of the 576,000 accounts to buy subscriptions and hardware, according to BleepingComputer.

Drain stored value and loyalty points. Balances, points and gift cards are attractive because they can be spent or transferred without a card check. The New York Attorney General's 2020 settlement with Dunkin' concerned credential stuffing against accounts holding stored-value cards, and required Dunkin' to refund stolen funds. Points farming and fake-account abuse of the same programmes is covered in loyalty programme automation.

Sell the account. Working logins are a product in their own right. BleepingComputer reported compromised Roku accounts being sold for as little as 50 cents.

Take the data. Some accounts are valuable for what they can see rather than what they can spend. Through about 14,000 accounts taken over by credential stuffing, the attacker in the 2023 23andMe incident reached profile data on about 6.9 million people who shared data with those accounts.

Lock the owner out. Changing the email, phone number and password keeps the real owner from recovering the account or noticing the theft until it is too late. The FBI notice describes attackers resetting the password and then wiring funds to accounts, "many of which are linked to cryptocurrency wallets".

Account takeover signals at login and after

Takeover shows up in two places, and each needs watching separately.

At login:

  • The ratio of failed to successful logins rises across the site, even if no single IP address crosses a limit.
  • Logins arrive through residential proxies, datacentre networks or VPNs that your real customers rarely use.
  • One device or connection logs in to many different accounts.
  • Logins for accounts that have been dormant for months appear in a burst.
  • The same account is reached from two distant places in a short time.

After login:

  • Email, phone number or password changes soon after a login from a new device.
  • A new delivery address, followed by an order paid with a saved card.
  • Points, gift card balances or stored value redeemed or transferred all at once.
  • Account recovery or password reset requests for many accounts from the same source.

Bot management stops the automated routes, not phishing or SIM swap

Bot management stops the automated routes in. Credential stuffing and password spraying only pay off at scale, so they depend on sending large numbers of login attempts, and stopping that automation at the login, the auth API, password reset and account recovery removes the routes that produce takeovers in bulk. It also cuts off account-checker tools that sort a combo list into working and failed logins, and automated probing of reset forms to find which emails have accounts.

Bot management does not stop the attacks that target one person:

  • a customer phished into typing their password and one-time code into a fake site, then a person logging in with them
  • a SIM swap at the customer's mobile carrier, which lets the attacker receive SMS codes legitimately
  • malware on the customer's own computer stealing a session cookie

For those, the defences are phishing-resistant authentication such as passkeys, which will not sign in to a look-alike domain; avoiding SMS as the only second factor; and checks after login, such as notifying the owner of every change to contact or payment details and asking for re-authentication before high-value actions.

The useful signals for stopping the automated attacks are network and connection based, because takeover tools run through residential proxies and anti-detect browsers that report whatever browser details the operator chooses. IP reputation, whether the connection comes through a proxy, the TLS fingerprint of the client and how the visitor interacts with the page are much harder to fake than what the browser claims about itself.

Account takeover prevention checklist

  1. Offer MFA, and prefer passkeys. See multi-factor authentication for the options. Roku and 23andMe both turned on two-factor authentication for all users after their incidents.
  2. Check new passwords against breach lists, as NIST SP 800-63B requires of verifiers.
  3. Rate-limit by account, device and network, not only by IP address, so attempts spread across a proxy pool still add up.
  4. Detect bots on every way in: login form, auth API, password reset and account recovery, not only the login page.
  5. Notify the owner of every change to email, phone, password or payment details, using the old contact details as well as the new ones.
  6. Add a check before high-value actions on a session that has just changed contact details or logged in from a new device, such as redeeming points, adding a delivery address or transferring a balance.
  7. Monitor the login success ratio and alert when it shifts.
  8. Make recovery as strong as login. A reset flow that asks for less than the login is the easier way in.

How Prosopo defends against account takeover

Prosopo sits in front of every authentication endpoint and scores every request against the patterns that account-takeover infrastructure leaves behind:

  • How the visitor behaves. Mouse movement, scroll rhythm and typing cadence. Automation repeats itself in ways a person does not, and that holds even when every other detail about the session looks ordinary.
  • Where the traffic really comes from. Attackers route through home broadband connections and racks of real phones so each request looks like a separate ordinary visitor. Residential proxy detection recognises those networks even when the individual address has no history.
  • Surge detection on auth endpoints. Unusual bursts from hosting networks or out-of-country ASNs automatically trigger an extra verification step for that traffic, while legitimate sign-ins are left alone.
  • Detection that moves during the attack. When an operator changes tactics mid-attack, the platform adjusts while it is still happening rather than in a write-up afterwards.
  • GDPR-compliant by design. No tracking cookies, EU-hosted on request, GDPR-compliant data handling out of the box.
  • Invisible for real users and trusted agents. Legitimate users and password-manager / AI-agent sessions sign in unimpeded; suspicious sessions get a proof-of-work or image challenge; known-bad traffic is blocked outright.

Real account holders sign in without interruption, trusted agents keep their access, and takeover infrastructure is stopped at the login form.

Account takeover protection at a financial provider

A financial provider guarding customer balances at login: 2,644,299 sessions scored, 23.67% stopped as automated, and a tenth of everything blocked was running an automation driver with no attempt at disguise. Another 22,091 blocks in thirty days were sessions where the attacker had paid a commercial service to solve the challenge for them. The full figures are in the financial provider case study.

Choosing account takeover protection software

Check these before you compare prices:

  • Every way in is covered. The login form, the auth API your mobile app calls, password reset and account recovery. A product that only sits on the login page leaves the reset flow open.
  • It runs before your origin. Prosopo Protect adds edge protection on Cloudflare Workers or AWS Lambda@Edge to the script tag on your pages, so requests are checked before they reach your login or auth API.
  • Every block has a reason. Your fraud team needs to see why a login was stopped, such as a solver service or an automation driver, not a risk score.
  • It shows you the false-positive rate. A blocked customer does not open a ticket; they leave. Ask for the false-positive rate alongside the catch rate.
  • The price is published. Protect starts at $1,990 a month, priced by your number of sites, SLA and data requirements rather than per request.

What to use

  • Enterprise (Prosopo Protect) — bot checks on login, password-reset and account-recovery endpoints: a script tag on your pages, with edge protection on Cloudflare Workers or AWS Lambda@Edge.
  • Bot Protection — apply risk-tiered policies per action, with the strictest checks reserved for high-value endpoints.
  • Access Control — restrict suspicious regions, hosting networks and known-bad fingerprints from reaching the login layer.

Comparing account takeover vendors? The vendor comparison page sets out how Prosopo, DataDome, HUMAN, Kasada and Arkose Labs each handle it, and what each costs.

Get a free account takeover assessment

Leave your work email and an engineer will look at how exposed your site is to account takeover, then get back to you within two working days with what they find and how Prosopo would handle it.

Work email only. We use it to answer this request. See our privacy policy.

Prefer a call? Book an assessment

Questions

Something else? Ask an engineer.

What is account takeover?

Account takeover (ATO) is when someone other than the owner gets into an online account and uses it as if they were the owner. The attacker usually gets in with a stolen or guessed password, a phished login and one-time code, a hijacked phone number or a stolen session cookie, and then changes the email or password so the real owner is locked out.

What is account takeover fraud?

Account takeover fraud is the money-making step after the break-in: spending a saved card, moving a balance, redeeming loyalty points or gift cards, or selling the account on. The FBI's Internet Crime Complaint Center said in November 2025 that it had received more than 5,100 complaints of ATO fraud since January 2025, with losses over $262 million, in a scheme where criminals impersonate bank support staff.

What is account takeover prevention?

Account takeover prevention stops attackers getting into real users' accounts. Most takeover attempts are automated: bots replay usernames and passwords leaked from other sites against your login form and auth API. Prevention means spotting that automation on every login, password-reset and account-recovery request, and stopping it before a password is checked, while real users sign in as normal.

Can bot protection reduce account takeover attempts?

Yes, because nearly all account takeover at scale is automated. Credential stuffing needs millions of login attempts to find the few that work, and bot protection stops those attempts at the login form, the auth API or the CDN edge. At one financial provider, Prosopo scored 2,644,299 sessions and stopped 23.67% of them as automated.

Can bot management stop account takeover?

It stops the automated part, which is most of it. Bot management blocks credential stuffing, password spraying and account-checker tools before they reach your authentication logic. It does not replace multi-factor authentication or phishing defences, which handle the attacks where a person hands over their own password.

How do you detect account takeover attacks?

Look at how each login request arrives rather than just whether the password was right. Signs of a takeover attack include login bursts from home broadband or mobile networks that have never used your site, automation drivers in the browser, typing and mouse movement that repeat exactly, and sessions that paid a commercial service to solve the CAPTCHA. Prosopo names the signal that caused each block.

What is the best account takeover protection for an enterprise?

One that covers every way into an account, not just the login page: the login form, the auth API, password reset and account recovery. Prosopo Protect covers all of them from one portal, from $1,990 a month, priced by your number of sites, SLA and data requirements rather than per request, and every block comes with a reason your fraud team can read. DataDome, HUMAN, Kasada and Arkose Labs are the other specialists to compare; see the vendor comparison page.