Chainalysis says breach exposed hashes and live tokens for all users
Chainalysis says names, usernames, password hashes and live tokens for every user were exposed; key services went offline as the firm tightened access controls.
The QNews Desk3 min read
What did attackers obtain from Chainalysis? The company says names, usernames, password hashes and live tokens for all its users were exposed to a malicious actor, expanding an October security incident into a breach affecting every account. In its security incident updates, Chainalysis said it found the exposure on Monday, Nov. 2, and disclosed it on Wednesday, Nov. 4.
The exposure raises account security concerns across Chainalysis’s customer base, while the company says it has found no evidence that investigation data was accessed or its blockchain attribution data altered.
How did the incident widen from the initial disclosure?
Chainalysis first reported the incident on Oct. 30, saying an external actor had used “offensive agentic techniques” to access its systems and internal tools. Its initial notice said some customer data, including user IDs, names, email addresses and organizational roles, had been accessed, while the company reported no evidence at that stage of unauthorized access to investigation content, credentials or session tokens. The notice described that identity information as non-sensitive.
On Nov. 4, the company said a separate “on-path attack” had exposed passwords for a subset of customers. An on-path attack occurs when an attacker gains access to infrastructure carrying communications between two parties; Chainalysis said it had contained and remediated that attack vector. Later that day, the firm disclosed that names, usernames, password hashes and live tokens for all users had been exposed.
Ars Technica’s report noted that Chainalysis has not specified where the on-path compromise occurred or whether the intercepted traffic was encrypted. The company has not published a total number of affected accounts, nor detailed how the earlier password exposure relates to the later disclosure covering all users. The confirmed scope is the four categories named in its update, not a count of individual people or organizations.
What does Chainalysis say attackers accessed?
The company says it has no evidence that investigation data—such as graphs, notes or cases—was accessed, or that its attribution data was manipulated. Those systems are central to Chainalysis’s work tracing cryptocurrency transactions and supporting investigations, so the distinction matters: confirmed exposure of account-related information does not establish that investigative records or transaction results were taken. The investigation remains ongoing.
Password hashes are cryptographic representations used to verify passwords; they are not passwords in clear text. However, their exposure can create risk if attackers can crack them, particularly where a password has been reused. A live token may also allow access to a service, depending on its type, permissions and whether it remains valid; Chainalysis has not publicly explained what its exposed tokens could access.
Which services were affected, and what is the current status?
After detecting abnormal activity, Chainalysis took its login page, Know Your Transaction (KYT) interface and API, and address-screening products offline. Reactor and Data Solutions had already been taken offline while the company investigated. Chainalysis said some KYT accounts appeared to have been accessed without authorization and that it was directly notifying those customers.
In its Nov. 7 update, Chainalysis said Reactor, KYT and Address Screening were back online with enhanced security measures. The company required users to reset passwords and rotate API keys as applicable, and asked customers to reconnect using instructions sent by email. Its update said it was still working to restore Data Solutions; the public notices did not provide a final account of how the attacker gained access or what the exposed tokens enabled.
Sources
- security incident updates — chainalysis.com
- Ars Technica’s report — arstechnica.com