In early November 2026, two blockchain-infrastructure companies disclosed breaches that exposed customer password data: Chainalysis on 6–7 November and Chainstack on 3 November. Neither incident is a reason to panic — both are a reason to act, methodically, in the next half hour.
This page is the working summary: what was actually exposed, why a leaked password hash matters, and what to do in order. Facts only; nothing here is speculation.
What happened
Two separate disclosures, days apart, with the same core problem for users:
- Chainalysis (disclosed 6–7 November 2026). The blockchain-analytics firm confirmed that an attacker exposed every user's name, username, password hashes and live authentication tokens, and that some passwords were leaked in plaintext. The company locked affected accounts, required password resets and API-key rotation, and suspended its KYT and address-screening services while restoring access. Reported by The Hacker News and TokenPost.
- Chainstack (disclosed 3 November 2026). The blockchain-infrastructure provider confirmed access to a customer database holding organization names, member email addresses and password hashes, plus systems holding node credentials. Its guidance explicitly includes changing the password on any other service where the same password was reused. Reported by The Hacker News.
Both incidents have been linked by investigators to a broader AI-agent attack campaign that abused exposed cloud credentials and API endpoints — the mechanics matter to the vendors' security teams, not to your response. Your response is the same either way.
Who should act: anyone with a Chainalysis or Chainstack account — and, just as important, anyone who reused that password anywhere else. Password reuse is how one vendor's breach becomes an attacker's list for every other account you own. That attack has a name: credential stuffing.
Why a leaked password hash is not "just a hash"
Vendors store passwords as hashes precisely so that a stolen database is not a stolen password list. That protection is real — but it is a speed bump, not a wall:
- Fast hashes fall fast. If a hash is not memory-hard (bcrypt/Argon2), a modern GPU rig tests ~10¹¹ guesses per second against it. The entropy of your password is the only thing slowing that down.
- Some passwords skip the line. Chainalysis disclosed that a subset of passwords was exposed in plaintext — no cracking required at all.
- Tokens beat passwords. Live authentication tokens were also exposed in the Chainalysis incident — which is why the company forced logouts and key rotation, not just resets.
- Reuse multiplies everything. A cracked or plaintext password is only useful to an attacker if it opens something else. Unique passwords make each breach a one-account problem.
What to do, in order
Work down the list. It takes about half an hour.
- Change the password on the breached account — via the vendor's own site or app, typed or bookmarked, not through a link in an email. Chainalysis customers: the company is rolling out resets as access restores; do it the moment you can. Chainstack customers: reset now and rotate API keys and node credentials if you use them.
- Change your email password next — if the breached password was reused on your email, that is the account attackers actually want: it resets everything else. Your email comes second on the list, always. (Full breach-response playbook.)
- Replace every reused copy with a unique one. Anything that shared that password is now on the list. If that sounds like too many passwords to remember — it is; that is what a password manager solves. (Why password managers are worth it.)
- Turn on 2FA everywhere it matters — email first, then anything financial. An authenticator app or passkey beats SMS where you have the choice. (Where SMS 2FA falls short.)
- Check what else is exposed — run the passwords you care about through the local breach check (zero-knowledge; the password never leaves your browser) and see whether they appear in older public breaches with the full leaked-password check.
- Expect a phishing wave. Breach news reliably brings fake "your account is compromised — reset now" emails. The reset lure is perfect because it is what a real response looks like. Type vendor addresses yourself; treat any reset link you did not request as hostile.
What not to do
- Don't click reset links in emails or DMs. Real resets are requested by you, from the site you typed yourself. Attackers time these waves to the breach news cycle.
- Don't "check" a breached password on random sites. Breach-checking is exactly the kind of thing that should run locally — ours does, in your browser, with a 5-character k-anonymity query and nothing else.
- Don't reuse the replacement. A new password that appears on three sites is the old problem with a new timestamp.
- Don't wait for the vendor's email. If you know you had an account, you do not need a notification to act.
If you were not a customer
You can stop reading here if you never had a Chainalysis or Chainstack account — but if this is the first time the "hash leak → reuse" chain has been explained, take the one habit that prevents it: never reuse a password across accounts. The credential-stuffing explainer shows exactly how the chain works. The password generator builds a unique replacement in one click, and the password health audit tells you how exposed your current setup is.
Frequently asked questions
Was my password leaked in the Chainalysis breach?
Chainalysis stated that every user's name, username and password hash was exposed, and that some passwords were exposed in plaintext. If you had a Chainalysis account, treat the password as compromised and everything that reused it as compromised too.
What can someone do with my password hash?
They can run guessing attacks against it offline, at hardware speed, until it matches — which is a question of your password's entropy, not of luck. And a cracked password is then replayed against your other accounts wherever it was reused. Changing the password on the breached service and everywhere it was reused ends the exposure.
Do I need to change my password if I used a strong, unique one?
Yes for the breached account itself — the hash and live tokens were exposed, and some passwords were in plaintext regardless of strength. If the password was truly unique, other accounts are not affected; the change is a single-account chore, which is exactly what uniqueness buys you.
The vendor already forced a reset. Am I done?
Done with that account, yes. Not done with reuse: if that password (or a close variant) exists anywhere else, those accounts are next on the list. Work through the ordered steps above once, and the whole family of incidents stops being your problem.