Chainalysis says password hashes and live tokens for every user were exposed
Short answer
Chainalysis’s own incident page, updated through November 10, 2026, says an attacker using what the company called offensive agentic techniques reached its systems in October. By the night of November 4 the company said names, usernames, password hashes, and live tokens for all Chainalysis users had been exposed. It also said it still had no evidence that investigation data was accessed or that blockchain attribution data was manipulated. Reactor, KYT, and Address Screening were taken offline and later restored with mandatory password resets and API-key rotation.
Last updated · Sekrd Research
- When: first public notice October 30, 2026. The all-users credential finding is the November 4, 2026, 11:00 p.m. EST update. Data Solutions was back online in the November 10 update.
- Who: Chainalysis, the blockchain analytics company. The page is written by the Chainalysis Team. No attacker name is given.
- Impact: names, usernames, password hashes, and live tokens for all Chainalysis users, per the November 4 night update. Earlier the same day, an “on-path attack” had exposed a subset of customer passwords.
- What was not claimed: as of that update, no evidence that investigation content was accessed or that attribution data was manipulated. The October 30 note said the incident was not the Binance crypto theft.
- Status: KYT, Address Screening, and Reactor were restored by November 7. Data Solutions was restored November 10. Every user was required to reset passwords and rotate API keys before registering transactions.
What happened
Chainalysis spent eleven days correcting its own public account of a breach, in writing, on one page. The October 30, 2026 notice said an external actor had used “offensive agentic techniques” to gain unauthorized access to Chainalysis systems and internal tools. At that moment the company said it had found no indication of unauthorized access to investigation content, transaction or query results, passwords in clear text, MFA secrets, or user session tokens. What it did confirm was access to non-sensitive profile data: user IDs, full names, email addresses, and organization role labels.
That description did not hold. On the morning of November 4, Chainalysis said an “on-path attack” had exposed a subset of customer passwords and that those accounts were being locked. The same morning it took KYT and the login page offline. Reactor, Data Solutions, and Chain (Beta) were already offline.
At 11:00 p.m. EST on November 4 the scope changed again. The company wrote that on Monday it had discovered that names, usernames, password hashes, and live tokens for all Chainalysis users were exposed to a malicious actor. It said it continued to have no evidence that any investigations data had been accessed or that Chainalysis attribution data had been manipulated. It also said it was notifying customers whose KYT accounts appeared to have been accessed without authorization.
A password hash still has to be cracked. A live token can be presented until it is revoked. Chainalysis did not say which systems the tokens unlocked, how passwords were hashed, or how many accounts were used. Those details are not on the page.
Timeline
- October 30. First customer email and blog update. Agentic access to internal systems. Profile fields accessed. No evidence, at that date, of credential or session-token access. Explicitly unrelated to the Binance theft.
- November 2. Reactor and Data Solutions taken offline for further assessment. Transaction-monitoring products kept running, with monitoring for unusual activity.
- November 4, 9:50 a.m. EST. On-path attack confirmed for a subset of passwords. Those customers told to reset, and to reset the same password anywhere else it was reused. The email says go to the Chainalysis login page directly rather than using links in password-reset mail.
- November 4, 10:30 a.m. EST. KYT and the login page taken offline because of abnormal activity. Password resets from the morning email could not be completed while login was down.
- November 4, 11:00 p.m. EST. Names, usernames, password hashes, and live tokens for all users. KYT restoration planned for the next day, behind an IP allowlist, with mandatory password and API-key rotation.
- November 6, 3:30 a.m. EST. Phased restoration of KYT and Address Screening begins.
- November 7, 1:50 p.m. EST. Reactor, KYT (UI and API), and Address Screening back online, with what the company called enhanced security measures.
- November 10, 3:00 a.m. EST. Data Solutions back online. Customers being brought back with account and data security as the stated priority.
What “offensive agentic techniques” does and does not tell you
The October 30 email is the only place Chainalysis describes the method, and it does not name a model, a bug, or a CVE. Later updates add an on-path attack against a subset of passwords and, separately, hashes and live tokens for every user. A password reset does not revoke a live token. Restoration required an IP allowlist, a password reset, and an API-key rotation before transactions could be registered again. The morning email also says not to trust password-reset links. Profile data was the early confirmed impact. Credential material for every user was the later one.
How to check if your app is exposed
- If you are a Chainalysis customer, follow the company’s email and open the usual login page directly. The November 4 note says not to use links in password-reset mail. Send trusted IPs to support@chainalysis.com. Reset the password and rotate keys before you register transactions. If the morning email named your account, reset that password anywhere you reused it.
- If you build a product that issues API tokens, assume a password reset does not end a session or kill a token. List every token type you store: personal access tokens, webhook signing secrets, OAuth refresh tokens, “live” API keys embedded in customer automations. A breach notice that says “reset your password” is incomplete unless those are revoked too.
- Look at your own logs for use of Chainalysis keys you stored in an app, a script, or an environment variable. The company’s page does not say customer-side integrations were scanned. If you copied a Chainalysis API key into a server, rotate it there after you rotate it in Chainalysis.
- Read the November 4 night update as the credential finding. Chainalysis has repeated that it has no evidence investigation content or attribution data was accessed or changed. That is a statement of its evidence, not a proof outsiders can re-run.
How Sekrd helps
Sekrd does not scan Chainalysis, and it cannot tell you whether your Chainalysis token was in the set the company described. It can tell you whether an API key of the same general kind is sitting in the JavaScript you ship. A free scan reports known provider key formats and a client-prefixed server secret. See secret-pattern-match and js-client-secret-env, and the rotation steps in the leaked-key guide.
The Railway incident, the week before this disclosure widened, is the other half of the same operational lesson: a platform that stores customer AI keys is a single place to steal many of them. That write-up is here. If the app you just generated stores third-party tokens, run a free scan of the deployed URL before you send users to it.
Related reading
- Railway’s October 21 AI-key theft
- ConnectWise Cloud Backup and Microsoft 365
- How Sekrd compares with other reviewers of AI-built apps
Frequently asked questions
What did Chainalysis say was exposed?
The November 4, 2026, 11:00 p.m. EST update says names, usernames, password hashes, and live tokens for all users. The October 30 notice had said credentials were not accessed. The later update is the credential finding.
Did attackers change Chainalysis attribution data?
Chainalysis says it has no evidence that investigation data was accessed or that attribution data was manipulated. That sentence is in the November 4 night update and is not withdrawn on November 6, 7, or 10.
What is the on-path attack Chainalysis described?
On the morning of November 4 the company told a subset of customers that an on-path attack had exposed their passwords and that those accounts were locked until a reset. It did not publish a technical write-up.
Are Chainalysis products back online?
The company’s November 7 update says Reactor, KYT, and Address Screening were back. The November 10 update says Data Solutions was back. Restoration required an IP allowlist, a password reset, and API-key rotation before registering transactions.
Was this the Binance theft?
Chainalysis’s October 30 notice says the incident is not related to the crypto theft at Binance. The page does not describe Binance further.
Sources
Don't ship until you're sekrd
Run a free scan to find the vulnerabilities your AI missed.
Scan Your App Free