Skip to main content

Account Fraud

TL;DR
  • Account fraud means fake or malicious accounts created on your platform
  • Types: Bot signups, referral abuse, multi-accounting, fake reviews
  • It can be infrastructure for what comes next, and signup rewards, messages and verification can cost you before that
  • Detect via: device fingerprinting, email analysis, behavioral patterns
  • Prevent with: CAPTCHA, email verification, phone verification, rate limiting

Not every signup is a customer. A fake account can be the setup for something later. You may see this called application fraud, which means something broader in lending and onboarding (classification).

Account fraud is fake or abusive accounts on your site or app. They can cost you at signup, through rewards, messages and verification (Twilio Verify's pricing shows one way that's billed). The bigger trap is what they enable: promo abuse, refund fraud, fake reviews and organized attacks.

Why Fake Accounts Matter​

They EnableHow
Promo abuseNew account = new discount
Referral fraudSelf-refer across accounts
Velocity evasionSpread activity across accounts
Card testingDisposable accounts for testing
Fake reviewsBoost or attack products
Limit evasionGetting around a purchase limit with extra accounts. Bulk buying for resale isn't fraud by itself

Common Patterns​

Bot Signups​

Automated signups at scale:

  • Hundreds of accounts in hours
  • Similar registration patterns
  • Disposable email domains
  • Generic or random usernames

Referral Fraud​

Gaming referral programs:

  • Self-referral across accounts
  • "Referral farms" with fake accounts
  • Quick signup → claim reward → abandon

Multi-Accounting​

One person, multiple identities:

  • Evade account-level limits
  • Stack promotions
  • Bypass bans or restrictions
  • Separate fraud activity from "real" account

Fake Review Fraud​

Social proof that isn't.

  • Paid review rings
  • Competitor sabotage
  • Boosting new products artificially

Detection Signals​

Compare these with your real signups and your program's terms, and check shared devices and autofill before you assign a motive.

Registration Red Flags​

SignalPriority to Check
Disposable email domainNext
Email pattern matches prior confirmed fraudFirst
Device seen on multiple accountsFirst, once you've ruled out a shared, work or public device
Signup form completed faster than a person could type itNext. Autofill does this too
Phone number from an internet calling (VoIP) providerNext
Similar usernames across accountsNext

Email Analysis​

PatternWhat It Suggests
john+1@gmail, john+2@gmailPossibly multi-accounting. Plus addresses are also a normal feature
Random string @domain.comPossibly bot-generated
Recently registered domainCheck its age against your own signup history; a new domain alone doesn't establish fraud
Known disposable domainPossibly a temporary account
Email with no history in your enrichment provider's sourcesInvestigate with the other signup signals. Little history doesn't prove the account is fake

Device Signals​

Device fingerprinting (what it reads) can link accounts. The other signals depend on what your integration returns, so ask which fields you get and how sure they are:

  • Same device across multiple accounts
  • Emulator or automation tools, if your provider detects them
  • VPN/proxy usage, if your provider detects it
  • A reputation flag on the device, if you buy one. A match isn't confirmed fraud

Behavioral Indicators​

BehaviorWhat It Could Be
No browsing before checkoutPossibly a script. Or a customer following a link
Immediate promo redemptionPossibly promo farming. Or someone who came for the promo
Referral link used instantlyPossibly self-referral. Or a friend who sent it
Never returns after signupPossibly a throwaway account. Real signups can do this too
Review posted without purchasePossible fake review

Prevention Strategies​

At Registration​

None of these stops everything, so expect errors and workarounds.

ControlWhat It Does
CAPTCHAChallenges suspected bots (how reCAPTCHA scores work)
Email verificationChecks access to the address. A disposable or attacker-controlled address can still pass
Phone verification, plus a limit on reusing a numberMulti-accounting gets harder: each account needs a different verified number. A verified number doesn't identify a unique person
Rate limitingSlows mass registration
Device fingerprintingLinks repeat registrations

Email Verification Best Practices​

LevelMethodWhat It Does
BasicSend confirmation linkChecks the customer can reach that address (Twilio's flow is one)
MediumApply a disposable-domain ruleRejects the domains it matches
StrongEmail risk scoringScores the address. A score doesn't prove fraud

Phone Verification​

CheckWhy
SMS verificationShows access to that number, not who holds it
VoIP detectionFlags virtual numbers. Some real customers use them
Phone line typeMobile vs. landline vs. VoIP
Phone velocitySame number, many accounts

Device Controls​

Use the device signals above here too. Each one is a reason to look closer, not proof.

Account Linking​

Here's what links accounts back together:

AttributeWhat It Links
Device fingerprintSame device across accounts. Check shared households before calling it one person
IP addressSame network (less reliable)
Payment methodSame card across accounts
Shipping addressSame destination
Behavioral patternsSimilar navigation, timing

Response Playbook​

Confirmed Fake Account​

  1. Block the account: Prevent further activity
  2. Revoke benefits: Cancel promos, referral rewards
  3. Block the identifiers: Device, email, phone, on your own block list
  4. Check for linked accounts: Find the network
  5. Update rules: Close the registration gap

Mass Signup Attack​

  1. Enable rate limiting: Slow the attack
  2. Add friction: CAPTCHA, phone verification
  3. Review recent signups: Find and remove fakes
  4. Block infrastructure: IPs, devices, email patterns

Prevention Checklist​

  • CAPTCHA on registration
  • Email verification required
  • Disposable email domains reviewed. Some real customers use them
  • Device fingerprinting enabled
  • Rate limiting on signup endpoints
  • Phone verification for high-value actions
  • VoIP and virtual numbers flagged for review. Some real customers use them
  • Account linking across devices
  • Promo redemption limits per device

Next Steps​

Preventing fake accounts?

  1. Add device fingerprinting: Catch repeat registrations
  2. Implement email verification: Check the address works
  3. Set up rate limiting: Slow mass signups

Detecting fake accounts?

  1. Check registration signals: Score risk at signup
  2. Analyze email patterns: Catch multi-accounting
  3. Link accounts: Find networks

Responding to fake accounts?

  1. Follow response playbook: Block and revoke
  2. Find linked accounts: Catch the full network
  3. Update prevention: Close gaps

Something wrong on this page? Email matt at paymentsandrisk.com and say what needs fixing.