Back to blog

Breach Response

Does a Password Breach Warning Mean My Account Was Hacked?

November 3, 2026 · 5 min read

No—but change it if you still use it.A breach warning means that password has appeared in leaked data. It does not prove someone signed in to your account. Replace it wherever you use it, then check your account activity.

What does your alert actually mean?

Four alerts, and what to do about each

Password found

This password appears in exposed data.

Does not identify your account or prove a login.

Replace it wherever you use it.

Email in a breach

Your address appears in a service’s leaked data.

Does not prove someone later signed in.

Review what was exposed and secure that account.

Failed login or reset email

A sign-in attempt failed, or you received a reset email you did not request.

Neither alert alone proves someone got into your account.

Open the service directly to check for successful sign-ins.

Unfamiliar account activity

A successful sign-in or account change you do not recognize.

Needs investigation, even if a password lookup is clear.

Open the service directly and review activity.

A “not found” result does not guarantee safety. A password can still be reused, easy to guess, or stolen in a leak this database does not contain.

Why a password match is not proof of an active hack

A password-only search cannot tell you which of your accounts used that password, who chose it, or whether anyone tried it. Three details help explain the result:

  • The leak may be old. A password can remain in a breach collection for years. A match today does not mean a new leak happened today, or that someone just used it to sign in.
  • Common passwords belong to many people. A generic choice such as password123 can appear many times because different people used it, sometimes across multiple services. The count records sightings in the data—not attacks against you or a count of your accounts. Even a word you have never used can return a match. Do not use this published example.
  • Changing a password does not erase earlier leaks. A retired password can keep triggering a warning. What matters is that it no longer protects any of your accounts.

What to do next

  1. Replace the password everywhere you use it.

    Open the affected service directly and choose a unique replacement. Your password manager can generate and save one, or you can use our password generator. Search your saved accounts for places where you reused the old password and replace it there too. Prioritize your email account: it often controls password resets for other services.

  2. Review sign-ins and account settings.

    Look under settings such as “Security,” “Recent activity,” or “Your devices.” Check successful sign-ins, purchases, recovery email addresses, and phone numbers you do not recognize. Device names and locations can be approximate, so investigate rather than assuming every unfamiliar label proves a hack.

  3. End sessions you do not trust.

    If you suspect someone got in, use “Sign out of all devices” or remove unknown sessions where the service offers it. Changing a password does not always end existing sessions automatically. You may need to sign back in on your own devices afterward.

  4. Check for ways someone could keep access.

    For email, review forwarding addresses, filters, and rules that could copy or hide messages. Remove changes you did not make. Also review connected apps, app passwords, recovery details, and registered sign-in methods; revoke access you do not recognize. If you are locked out, start from the service’s official account recovery page.

  5. Add stronger sign-in protection.

    Use a passkey or a FIDO2/WebAuthn security key where supported: they resist fake sign-in pages. Otherwise, enable multi-factor authentication; an authenticator app is a useful option. Codes can still be phished, so never share them with someone who contacts you. Store recovery codes somewhere private so you can get back in if a device is lost.

How passwords.lu checks your password privately

You should not have to send a website your password just to find out whether it leaked. Our Password Breach Checker performs the sensitive parts in your browser and uses Have I Been Pwned for the lookup:

  1. Create a fingerprint locally. Your browser turns the password into a 40-character SHA-1 hash.
  2. Send only five characters. Have I Been Pwned receives the hash’s first five characters, which identify a group of possible matches rather than the full hash. This is called k-anonymity.
  3. Finish the comparison on your device. The service returns matching hash endings and their counts. Your browser checks which, if any, matches the rest of your hash.

This lookup sends neither your full password nor your full hash to either server. Have I Been Pwned does receive the prefix and connection information such as your IP address.

Extra padding adds privacy. Our checker requests extra results with a count of zero to make response sizes less revealing. These filler entries are ignored; they are not real password sightings.

Why use SHA-1 here?

SHA-1 matches the format of the Pwned Passwords dataset. It is not a recommendation for storing passwords. The checker requests padding with the Add-Padding header and excludes zero-count entries when checking for a match.

This design reduces what is shared; it does not make an untrusted device or website safe. Use a device you control and check the address before entering anything sensitive. A password manager’s built-in breach warning is another way to check without typing the password into a separate website.

Need help recovering an account?

Follow our full account recovery checklist if you find changes you did not make or need help deciding what to secure first.

Ready to replace an exposed password?

Generate a unique replacement, or open the recovery checklist if you found signs of account misuse.

Photo by Marc Marchal on Unsplash · Modified with AI