account takeover fraud

Blog /

Fraud & Abuse

What is Account Takeover Fraud, and How Do You Prevent It?

Account Takeover (ATO) fraud can be compared to someone quietly entering your account, changing your details, and using your funds, all while you’re left unaware. It’s a growing risk that can cause significant harm to businesses. Let’s take a look at how it works and how you can prevent it from affecting your platform.

Matias Berny

Founder

Summary

Account takeover (ATO) fraud is when an attacker logs into someone's existing account and uses it as their own. The FBI's 2025 Internet Crime Report counted about 4,700 ATO complaints in the US, with $359.7 million in losses. Prevention works in layers: block bad logins, add step-up checks before sensitive actions, protect account recovery, and revoke sessions fast. Prelude Auth provides step-up challenges, passkey and OTP verification, sessions bound to the user's browser or device, and session revocation.

A customer gets a text that looks like it's from their bank's fraud team. Minutes later, a caller asks them to read back a one-time code to "stop" a suspicious charge. By the time they hang up, the attacker has reset their password and is moving their money out.

That's account takeover fraud, and it's the pattern the FBI described in its November 2025 alert. Nothing was hacked. The attacker simply logged in as the customer. In 2025, the FBI’s Internet Crime Report logged about 4,700 account takeover complaints in the US, with $359.7 million in losses.

This guide covers how account takeover fraud works, the warning signs to watch for, how to prevent it in layers, and what to do after an account is hijacked.

What is Account Takeover fraud?

Account takeover (ATO) fraud is a form of identity fraud where a criminal gains control of a legitimate account that already exists, such as a bank login, a shopping account, or a loyalty account. Once inside, the attacker changes the password, email, or phone number to lock the real owner out, then moves money, makes purchases, or steals stored data.

The key word is existing. The attacker isn't creating anything new. They're borrowing the trust and history the account has already built up, which is why ATO is hard to spot: to your systems, the attacker looks like a returning customer.

If you've ever heard someone say their account was "hijacked" or "hacked," that's account takeover.

Account Takeover vs Identity Theft vs New Account Fraud

These terms overlap, so it helps to separate them:


What the attacker does

Example

Account takeover fraud

Takes control of an account that already exists

Logs into a customer's banking app with a phished password and code

New account fraud

Opens a new account using stolen or invented details

Signs up for a credit card in someone else's name

Identity theft

The broader crime of using another person's identity

Covers both of the above, plus tax and benefits fraud

ATO is one form of identity theft. New account fraud is another, and it's covered in Prelude's guide to new account fraud. If your problem is fake signups rather than hijacked logins, see how to prevent fake account creation.

How Does Account Takeover Fraud Work?

Most account takeovers follow the same three steps: get the credentials, get past the second factor, then lock the owner out.

Stolen credentials are still one of the main ways in. In its 2026 Data Breach Investigations Report, Verizon found that exploited software vulnerabilities have only now overtaken stolen credentials as the top breach entry point. The same report found that social engineering on mobile succeeds 40% more often than traditional email phishing. That matters for ATO, since the attacks the FBI describes in its November 2025 alert start with a text, call, or email.

Here are the methods attackers use most.

1. Credential stuffing

Attackers take username and password pairs leaked in earlier breaches and test them against other sites with bots. Wherever a person has reused a leaked password, the stolen pair works on the new site too. Prelude's guide to credential stuffing attacks covers how these bot campaigns work and how to stop them.

2. Phishing and fake support calls

This is the method the FBI highlighted in its November 2025 alert. Attackers contact victims by text, call, or email while posing as their bank, customer support, or tech support. They trick the victim into sharing their password and their one-time passcode, then reset the password and take over.

Some attackers buy search ads that imitate a real company's login page, so a victim who searches for their bank lands on a phishing site instead. The FBI calls this SEO poisoning.

3. Adversary-in-the-middle phishing and session hijacking

A phishing page can sit between the user and the real site, passing the login through and capturing the session cookie or token at the end. With that token, the attacker doesn't need the password or the code again. As the FBI puts it: "MFA will not protect you if you land on a fraudulent login page."

That's why session protection matters as much as login protection. Prelude Auth's web and mobile SDKs, for example, bind the refresh token to a private key that stays in the user's browser or device, so a stolen refresh cookie or token is unusable on its own.

4. SIM swapping

The attacker convinces a mobile carrier to move the victim's phone number to a SIM they control, then receives the victim's text messages, including verification codes. Prelude's guide on how to prevent SIM swapping goes deeper on this method.

5. Malware and infostealers

Keyloggers (malware that records what you type) and infostealers (malware that copies saved passwords and login cookies from a device) capture credentials straight from an infected computer or phone, then sell them or use them.

6. AI-assisted impersonation

Generative AI makes social engineering more convincing. In a July 2026 alert, the FBI warned that AI-generated voice clones "can sound nearly identical" to someone the victim knows. The goal is the same as any phishing call: get the victim to hand over a password or code.

Examples of Account Takeover Fraud

  • Banking: An attacker calls posing as the bank's fraud team, gets the customer to read out a one-time code, resets the password, and wires the balance out. The FBI notes that stolen funds often move quickly into accounts tied to cryptocurrency wallets, which makes recovery hard.

  • Ecommerce: An attacker logs in with a reused password, changes the shipping address, and orders high-value items on the saved card.

  • Loyalty and travel: An attacker redeems or transfers a victim’s airline miles or reward points.

  • Payroll: A fake payroll login page captures an employee's credentials, and the attacker redirects their direct deposit.

Who Is Targeted by Account Takeover Fraud?

Any account that holds money, stored payment details, or something that can be resold can be a target:

  • Financial services: bank accounts, payment apps, crypto exchanges, and payroll portals.

  • Ecommerce and marketplaces: saved cards, gift card balances, and seller accounts.

  • Travel and loyalty programs: miles and points that can be redeemed or transferred.

  • Telecom, gaming, and social platforms: accounts used for further fraud, resale, or impersonation.

Warning Signs of Account Takeover

ATO detection means spotting a change in context. Watch for:

  • Login spikes: a sudden rise in failed logins, especially across many accounts from the same IPs, points to credential stuffing.

  • New device or location right before a sensitive action: a login from a never-seen device followed by a payout or password change.

  • Account detail changes: a new email, phone number, or password reset the user didn't request.

  • Unusual transactions: high-value purchases, new payees, or withdrawals that don't match past behavior.

  • Several active sessions in different countries for the same user.

  • Support tickets from users saying they're locked out or got a code they didn't ask for.

Most of these signals show up at the moment of a sensitive action, which is where Prelude Auth's step-up hook sits: before a transfer or contact change, Prelude sends the app's backend the request's IP address, user agent, and platform, so the app can compare them with the original login and decide whether to challenge or block.

How to Prevent Account Takeover Fraud

Account takeover prevention works in layers. No single control stops every method above, so the goal is to make each step of the attack harder.

1. Make stolen passwords less useful

  • Check new and changed passwords against lists of known compromised passwords. NIST's digital identity guidelines (SP 800-63B-4) require this.

  • Rate-limit failed login attempts. NIST caps consecutive failed attempts at 100 per account and lets organizations set lower limits.

  • Detect bot traffic at the edge so credential stuffing runs into friction before it reaches your login form. Prelude Auth fingerprints clients at the network edge to tell browsers, mobile apps, and AI agents apart before they reach the auth flow.

2. Use multi-factor authentication, and offer a phishing-resistant option

With MFA, a stolen password alone isn’t enough to log in. But one-time codes can be phished, as the FBI alert shows, so NIST's guidelines say services should offer at least one phishing-resistant option, such as passkeys, at AAL2.

A practical setup is passkeys where users have them, with SMS or email codes as the fallback. Prelude Auth supports passkeys as a verification step with an OTP fallback for users who haven't registered one. For a broader comparison, see Prelude's guide to types of authentication methods and the role of SMS in MFA.

3. Add step-up verification before sensitive actions

Attackers who get past login still need to do something valuable: send money, change the email, add a new phone number. Step-up authentication asks for fresh proof right before those actions.

With Prelude Auth, an app can require a step-up challenge before actions such as transfers, password changes, or data exports. Prelude calls a hook on the app's backend with context about the request, including IP address, user agent, and platform, and the app decides whether to allow it, require an SMS, email, or passkey challenge, or block it. For high-risk actions, such as transfers, the extra permission can be set to single-use: it's attached to one access token only, isn't stored on the session, and expires after a set number of seconds.

4. Protect account recovery and contact changes

Password resets and contact changes are the moment attackers lock owners out. Treat them as sensitive actions:

  • Require verification before changing an email address or phone number.

  • Notify the old email and phone number when either one changes.

  • Verify any new phone number or email before it's attached to the account. In Prelude Auth, adding a phone number or email runs its own OTP challenge before the identifier is saved.

5. Protect sessions, not just logins

Since attackers can steal session tokens directly, bind sessions to the device where possible and keep them short-lived. Prelude Auth's web and mobile SDKs protect the refresh flow with DPoP (RFC 9449), so a stolen refresh token or cookie can't be used without a private key that never leaves the user's browser or device. Token reuse also triggers automatic revocation across all of the user's sessions.

Give users a list of their active sessions, with device and last-seen details, so they can spot one that isn't theirs. Prelude Auth exposes this list per user, and its mobile SDKs can also lock an idle session until the user re-enters a passcode or passes Face ID, Touch ID, or a fingerprint check.

6. Educate users

Tell users, in your own app and emails, that your company will never call or text to ask for their password or code. The FBI makes the same point: "Companies generally do not contact you to ask for your username, password, or OTP." Encourage them to use bookmarks rather than search ads to reach your login page.

Account takeover prevention checklist

Layer

What it stops

How Prelude Auth handles it

Block bad logins

Credential stuffing, password reuse

Network fingerprinting at the edge

MFA with a phishing-resistant option

Stolen passwords, phished codes

Passkeys, with SMS or email OTP fallback

Step-up before sensitive actions

Transfers, payouts, and contact changes after a hijacked login

Hook to the app’s backend with IP, user agent, and platform; SMS, email, or passkey challenge; single-use, time-limited grants

Protect recovery and contact changes

Attackers locking the owner out

New phone numbers and emails pass their own OTP challenge before they’re saved

Protect sessions

Stolen cookies and tokens

DPoP binding to the browser or device; mobile idle lock; session list and revocation

What to Do After an Account Takeover

Move fast: the FBI notes that stolen funds often move quickly, which makes recovery hard. A clear incident response plan for a hijacked account looks like this:

  1. Kill every session. Sign the user out everywhere so the attacker loses access. In Prelude Auth, revokeSessions("all") revokes every session for the user, and "others" keeps only the current one.

  2. Reset credentials and restore contact details. Force a password reset and roll back any email, phone, or recovery change the attacker made.

  3. Freeze high-risk actions. Pause payouts, transfers, and new payees until the owner is verified again through step-up.

  4. Contact the user on a known channel. Use the original email or phone on file, not anything the attacker added.

  5. Reverse what you can. For bank transfers, the FBI advises victims to contact their financial institution right away to request a recall or reversal.

  6. Report it. In the US, victims and businesses can file a complaint at ic3.gov. If your brand was impersonated, request takedowns of the phishing pages and warn other users.

  7. Find the entry point. Check whether it was a reused password, a phished code, a SIM swap, or a stolen session, and close that gap first.

Account Takeover Fraud Detection Tools

The tools that catch ATO all compare a request against what's normal for that user:

  • Risk-based authentication: raises the bar, for example with an OTP or passkey prompt, when a login or action looks unusual.

  • Device and network fingerprinting: recognizes returning devices and flags new ones, proxies, and automated clients. Prelude Auth uses network fingerprinting and device ID correlation for this.

  • Behavioral analytics: spots changes in typing, navigation, or transaction patterns after login.

  • IP geolocation: flags logins far from the user's usual locations.

  • Session management: shows active sessions per user and lets you revoke them on demand. In Prelude Auth, sessions can be revoked one at a time, all except the current one, or all at once.

FAQs

What is account takeover fraud?

Account takeover fraud is when a criminal gains control of someone's existing online account, for example with stolen or phished credentials, and uses it to steal money, make purchases, or take data. The attacker may then change the password or contact details to lock the real owner out.

What is the difference between account takeover and identity theft?

Identity theft is the broad crime of using someone else's identity. Account takeover is one type of it, where the attacker hijacks an account that already exists. New account fraud is another type, where the attacker opens a new account in the victim's name.

What are examples of account takeover fraud?

Common examples include an attacker posing as a bank's fraud team to get a one-time code and drain an account, logging into a shopping account with a reused password to order goods, or redeeming a victim's airline miles.

How do you prevent account takeover?

Use layered controls: block compromised and reused passwords, rate-limit logins, offer phishing-resistant MFA such as passkeys, require step-up verification before sensitive actions like transfers or contact changes, protect account recovery, and be able to revoke all of a user's sessions instantly. Prelude Auth provides the step-up, passkey, OTP, and session revocation pieces of this through one API.

Does MFA stop account takeover?

MFA blocks attacks that rely only on a stolen password, but one-time codes can still be phished. The FBI warns that MFA won't protect a user who enters their details on a fake login page. Phishing-resistant methods like passkeys, step-up checks on sensitive actions, and device-bound sessions close that gap. Prelude Auth supports all three, and can fall back to an SMS or email OTP for users without a passkey.

Stop Account Takeovers Before They Cost You

Account takeover fraud succeeds when a single stolen password or code unlocks everything. Prelude Auth adds layers that break that chain: passkey and OTP verification, step-up challenges before sensitive actions, sessions bound to the user's browser or device, and session revocation.

Start for free or talk to sales to see how Prelude Auth fits into your login flow.

A customer gets a text that looks like it's from their bank's fraud team. Minutes later, a caller asks them to read back a one-time code to "stop" a suspicious charge. By the time they hang up, the attacker has reset their password and is moving their money out.

That's account takeover fraud, and it's the pattern the FBI described in its November 2025 alert. Nothing was hacked. The attacker simply logged in as the customer. In 2025, the FBI’s Internet Crime Report logged about 4,700 account takeover complaints in the US, with $359.7 million in losses.

This guide covers how account takeover fraud works, the warning signs to watch for, how to prevent it in layers, and what to do after an account is hijacked.

What is Account Takeover fraud?

Account takeover (ATO) fraud is a form of identity fraud where a criminal gains control of a legitimate account that already exists, such as a bank login, a shopping account, or a loyalty account. Once inside, the attacker changes the password, email, or phone number to lock the real owner out, then moves money, makes purchases, or steals stored data.

The key word is existing. The attacker isn't creating anything new. They're borrowing the trust and history the account has already built up, which is why ATO is hard to spot: to your systems, the attacker looks like a returning customer.

If you've ever heard someone say their account was "hijacked" or "hacked," that's account takeover.

Account Takeover vs Identity Theft vs New Account Fraud

These terms overlap, so it helps to separate them:


What the attacker does

Example

Account takeover fraud

Takes control of an account that already exists

Logs into a customer's banking app with a phished password and code

New account fraud

Opens a new account using stolen or invented details

Signs up for a credit card in someone else's name

Identity theft

The broader crime of using another person's identity

Covers both of the above, plus tax and benefits fraud

ATO is one form of identity theft. New account fraud is another, and it's covered in Prelude's guide to new account fraud. If your problem is fake signups rather than hijacked logins, see how to prevent fake account creation.

How Does Account Takeover Fraud Work?

Most account takeovers follow the same three steps: get the credentials, get past the second factor, then lock the owner out.

Stolen credentials are still one of the main ways in. In its 2026 Data Breach Investigations Report, Verizon found that exploited software vulnerabilities have only now overtaken stolen credentials as the top breach entry point. The same report found that social engineering on mobile succeeds 40% more often than traditional email phishing. That matters for ATO, since the attacks the FBI describes in its November 2025 alert start with a text, call, or email.

Here are the methods attackers use most.

1. Credential stuffing

Attackers take username and password pairs leaked in earlier breaches and test them against other sites with bots. Wherever a person has reused a leaked password, the stolen pair works on the new site too. Prelude's guide to credential stuffing attacks covers how these bot campaigns work and how to stop them.

2. Phishing and fake support calls

This is the method the FBI highlighted in its November 2025 alert. Attackers contact victims by text, call, or email while posing as their bank, customer support, or tech support. They trick the victim into sharing their password and their one-time passcode, then reset the password and take over.

Some attackers buy search ads that imitate a real company's login page, so a victim who searches for their bank lands on a phishing site instead. The FBI calls this SEO poisoning.

3. Adversary-in-the-middle phishing and session hijacking

A phishing page can sit between the user and the real site, passing the login through and capturing the session cookie or token at the end. With that token, the attacker doesn't need the password or the code again. As the FBI puts it: "MFA will not protect you if you land on a fraudulent login page."

That's why session protection matters as much as login protection. Prelude Auth's web and mobile SDKs, for example, bind the refresh token to a private key that stays in the user's browser or device, so a stolen refresh cookie or token is unusable on its own.

4. SIM swapping

The attacker convinces a mobile carrier to move the victim's phone number to a SIM they control, then receives the victim's text messages, including verification codes. Prelude's guide on how to prevent SIM swapping goes deeper on this method.

5. Malware and infostealers

Keyloggers (malware that records what you type) and infostealers (malware that copies saved passwords and login cookies from a device) capture credentials straight from an infected computer or phone, then sell them or use them.

6. AI-assisted impersonation

Generative AI makes social engineering more convincing. In a July 2026 alert, the FBI warned that AI-generated voice clones "can sound nearly identical" to someone the victim knows. The goal is the same as any phishing call: get the victim to hand over a password or code.

Examples of Account Takeover Fraud

  • Banking: An attacker calls posing as the bank's fraud team, gets the customer to read out a one-time code, resets the password, and wires the balance out. The FBI notes that stolen funds often move quickly into accounts tied to cryptocurrency wallets, which makes recovery hard.

  • Ecommerce: An attacker logs in with a reused password, changes the shipping address, and orders high-value items on the saved card.

  • Loyalty and travel: An attacker redeems or transfers a victim’s airline miles or reward points.

  • Payroll: A fake payroll login page captures an employee's credentials, and the attacker redirects their direct deposit.

Who Is Targeted by Account Takeover Fraud?

Any account that holds money, stored payment details, or something that can be resold can be a target:

  • Financial services: bank accounts, payment apps, crypto exchanges, and payroll portals.

  • Ecommerce and marketplaces: saved cards, gift card balances, and seller accounts.

  • Travel and loyalty programs: miles and points that can be redeemed or transferred.

  • Telecom, gaming, and social platforms: accounts used for further fraud, resale, or impersonation.

Warning Signs of Account Takeover

ATO detection means spotting a change in context. Watch for:

  • Login spikes: a sudden rise in failed logins, especially across many accounts from the same IPs, points to credential stuffing.

  • New device or location right before a sensitive action: a login from a never-seen device followed by a payout or password change.

  • Account detail changes: a new email, phone number, or password reset the user didn't request.

  • Unusual transactions: high-value purchases, new payees, or withdrawals that don't match past behavior.

  • Several active sessions in different countries for the same user.

  • Support tickets from users saying they're locked out or got a code they didn't ask for.

Most of these signals show up at the moment of a sensitive action, which is where Prelude Auth's step-up hook sits: before a transfer or contact change, Prelude sends the app's backend the request's IP address, user agent, and platform, so the app can compare them with the original login and decide whether to challenge or block.

How to Prevent Account Takeover Fraud

Account takeover prevention works in layers. No single control stops every method above, so the goal is to make each step of the attack harder.

1. Make stolen passwords less useful

  • Check new and changed passwords against lists of known compromised passwords. NIST's digital identity guidelines (SP 800-63B-4) require this.

  • Rate-limit failed login attempts. NIST caps consecutive failed attempts at 100 per account and lets organizations set lower limits.

  • Detect bot traffic at the edge so credential stuffing runs into friction before it reaches your login form. Prelude Auth fingerprints clients at the network edge to tell browsers, mobile apps, and AI agents apart before they reach the auth flow.

2. Use multi-factor authentication, and offer a phishing-resistant option

With MFA, a stolen password alone isn’t enough to log in. But one-time codes can be phished, as the FBI alert shows, so NIST's guidelines say services should offer at least one phishing-resistant option, such as passkeys, at AAL2.

A practical setup is passkeys where users have them, with SMS or email codes as the fallback. Prelude Auth supports passkeys as a verification step with an OTP fallback for users who haven't registered one. For a broader comparison, see Prelude's guide to types of authentication methods and the role of SMS in MFA.

3. Add step-up verification before sensitive actions

Attackers who get past login still need to do something valuable: send money, change the email, add a new phone number. Step-up authentication asks for fresh proof right before those actions.

With Prelude Auth, an app can require a step-up challenge before actions such as transfers, password changes, or data exports. Prelude calls a hook on the app's backend with context about the request, including IP address, user agent, and platform, and the app decides whether to allow it, require an SMS, email, or passkey challenge, or block it. For high-risk actions, such as transfers, the extra permission can be set to single-use: it's attached to one access token only, isn't stored on the session, and expires after a set number of seconds.

4. Protect account recovery and contact changes

Password resets and contact changes are the moment attackers lock owners out. Treat them as sensitive actions:

  • Require verification before changing an email address or phone number.

  • Notify the old email and phone number when either one changes.

  • Verify any new phone number or email before it's attached to the account. In Prelude Auth, adding a phone number or email runs its own OTP challenge before the identifier is saved.

5. Protect sessions, not just logins

Since attackers can steal session tokens directly, bind sessions to the device where possible and keep them short-lived. Prelude Auth's web and mobile SDKs protect the refresh flow with DPoP (RFC 9449), so a stolen refresh token or cookie can't be used without a private key that never leaves the user's browser or device. Token reuse also triggers automatic revocation across all of the user's sessions.

Give users a list of their active sessions, with device and last-seen details, so they can spot one that isn't theirs. Prelude Auth exposes this list per user, and its mobile SDKs can also lock an idle session until the user re-enters a passcode or passes Face ID, Touch ID, or a fingerprint check.

6. Educate users

Tell users, in your own app and emails, that your company will never call or text to ask for their password or code. The FBI makes the same point: "Companies generally do not contact you to ask for your username, password, or OTP." Encourage them to use bookmarks rather than search ads to reach your login page.

Account takeover prevention checklist

Layer

What it stops

How Prelude Auth handles it

Block bad logins

Credential stuffing, password reuse

Network fingerprinting at the edge

MFA with a phishing-resistant option

Stolen passwords, phished codes

Passkeys, with SMS or email OTP fallback

Step-up before sensitive actions

Transfers, payouts, and contact changes after a hijacked login

Hook to the app’s backend with IP, user agent, and platform; SMS, email, or passkey challenge; single-use, time-limited grants

Protect recovery and contact changes

Attackers locking the owner out

New phone numbers and emails pass their own OTP challenge before they’re saved

Protect sessions

Stolen cookies and tokens

DPoP binding to the browser or device; mobile idle lock; session list and revocation

What to Do After an Account Takeover

Move fast: the FBI notes that stolen funds often move quickly, which makes recovery hard. A clear incident response plan for a hijacked account looks like this:

  1. Kill every session. Sign the user out everywhere so the attacker loses access. In Prelude Auth, revokeSessions("all") revokes every session for the user, and "others" keeps only the current one.

  2. Reset credentials and restore contact details. Force a password reset and roll back any email, phone, or recovery change the attacker made.

  3. Freeze high-risk actions. Pause payouts, transfers, and new payees until the owner is verified again through step-up.

  4. Contact the user on a known channel. Use the original email or phone on file, not anything the attacker added.

  5. Reverse what you can. For bank transfers, the FBI advises victims to contact their financial institution right away to request a recall or reversal.

  6. Report it. In the US, victims and businesses can file a complaint at ic3.gov. If your brand was impersonated, request takedowns of the phishing pages and warn other users.

  7. Find the entry point. Check whether it was a reused password, a phished code, a SIM swap, or a stolen session, and close that gap first.

Account Takeover Fraud Detection Tools

The tools that catch ATO all compare a request against what's normal for that user:

  • Risk-based authentication: raises the bar, for example with an OTP or passkey prompt, when a login or action looks unusual.

  • Device and network fingerprinting: recognizes returning devices and flags new ones, proxies, and automated clients. Prelude Auth uses network fingerprinting and device ID correlation for this.

  • Behavioral analytics: spots changes in typing, navigation, or transaction patterns after login.

  • IP geolocation: flags logins far from the user's usual locations.

  • Session management: shows active sessions per user and lets you revoke them on demand. In Prelude Auth, sessions can be revoked one at a time, all except the current one, or all at once.

FAQs

What is account takeover fraud?

Account takeover fraud is when a criminal gains control of someone's existing online account, for example with stolen or phished credentials, and uses it to steal money, make purchases, or take data. The attacker may then change the password or contact details to lock the real owner out.

What is the difference between account takeover and identity theft?

Identity theft is the broad crime of using someone else's identity. Account takeover is one type of it, where the attacker hijacks an account that already exists. New account fraud is another type, where the attacker opens a new account in the victim's name.

What are examples of account takeover fraud?

Common examples include an attacker posing as a bank's fraud team to get a one-time code and drain an account, logging into a shopping account with a reused password to order goods, or redeeming a victim's airline miles.

How do you prevent account takeover?

Use layered controls: block compromised and reused passwords, rate-limit logins, offer phishing-resistant MFA such as passkeys, require step-up verification before sensitive actions like transfers or contact changes, protect account recovery, and be able to revoke all of a user's sessions instantly. Prelude Auth provides the step-up, passkey, OTP, and session revocation pieces of this through one API.

Does MFA stop account takeover?

MFA blocks attacks that rely only on a stolen password, but one-time codes can still be phished. The FBI warns that MFA won't protect a user who enters their details on a fake login page. Phishing-resistant methods like passkeys, step-up checks on sensitive actions, and device-bound sessions close that gap. Prelude Auth supports all three, and can fall back to an SMS or email OTP for users without a passkey.

Stop Account Takeovers Before They Cost You

Account takeover fraud succeeds when a single stolen password or code unlocks everything. Prelude Auth adds layers that break that chain: passkey and OTP verification, step-up challenges before sensitive actions, sessions bound to the user's browser or device, and session revocation.

Start for free or talk to sales to see how Prelude Auth fits into your login flow.

Start optimizing your auth flow

Send verification text-messages anywhere in the world with the best price, the best deliverability and no spam.