Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Customers say their accounts on my site were taken over

Short answer

This is probably credential stuffing: attackers try email and password pairs stolen from other sites on yours, and real customers who reused a password get taken over. Your servers need not be breached. A second sign-in step, limits on automated logins and a check for known-leaked passwords are the main defences.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Customers say orders, points or details changed and they did not do it.
  • My login page gets a flood of attempts from many addresses.
  • The failed logins use real customer emails, many only once each.
  • Support is overwhelmed by password reset requests.
  • A few logins succeeded straight after a long list of failures.

Why does this happen?

  1. Customers reuse one password everywhere

    OWASP describes credential stuffing as testing username and password pairs obtained from the breach of another site. If your customer used the same pair, the attacker is simply let in.

  2. Each login looks normal

    Attacks spread across many addresses with one or two tries per account. Simple lockouts or blocking one address barely slow them down.

  3. A login page without a second step gives away everything

    OWASP names multi-factor authentication as the strongest defence, with CAPTCHA, graduated responses on addresses, device checks, breached-password checks and user notifications as further layers.

  4. Using the email as the username helps the attacker

    The same guide lists unpredictable usernames as a defence, since a leaked list of emails then does not match your login names.

What can I do about it today?

  1. Look at the logs before you actAsk your developer for failed and successful logins over the last days, grouped by address and by account.
  2. Reset the accounts that were taken overSign out their sessions and have the owner choose a new password through your normal reset.
  3. Offer a second sign-in stepStart as an option, or require it for risky actions like changing email or paying.
  4. Tell affected customers plainlySay their password may have been used on another site and ask them not to reuse it. Check with a lawyer whether any notice duty applies.
  5. Ask for limits on automated loginsA bot check after a few failures and limits per address help, in layers, tested with real users.
  6. Do not block whole countries in a panicIt can cut off real customers. Ask for changes that are tested first.

When should I bring someone in?

  • Money, stored cards or personal data were reached through taken-over accounts.
  • The attack volume is slowing the site down.
  • You cannot tell from your logs which accounts succeeded.

How do I handle it?

  1. Separate the attack from the damageI read the login logs to learn which accounts were guessed and which actions followed.
  2. Contain the affected accountsSessions are ended, and sensitive changes made after the suspicious login are listed for your review.
  3. Add layers at the loginLimits on rate, a bot check after failures, a check for known-leaked passwords and a second sign-in step, each tried with real accounts.
  4. Add notificationsCustomers are emailed on a new device or a changed email address, so takeovers are seen early.
  5. Watch the patternAn alert for a high share of failed logins, and for success right after many failures.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Was my database hacked?

Not necessarily. In credential stuffing the passwords come from a different site's breach, and your own system only sees valid-looking logins. The logs tell you which it is.

What single change helps most?

OWASP names multi-factor authentication as the strongest defence, but it works best together with limits on automated logins.

Do I need to tell my customers?

Telling affected customers to change passwords is sensible. Whether a formal notice is required depends on your location and the data, which a lawyer should answer.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.