What happened
Chainalysis's own timeline, in an update dated 2026-11-13, says the actor began exploiting a zero-day in a key third-party software vendor on 2026-08-20, which Chainalysis patched within three days of the vendor's fix. On 2026-10-15 automated scanning found a Data Solutions API endpoint "accessible more broadly than intended"; on 2026-10-22 detection alerts identified an external actor using agentic techniques to exploit an exposed self-registration workflow; and on 2026-10-24 it found the same actor had accessed an internal system exposed by the zero-day. The vendor has not been named.2
The company's public notice of 2026-10-30 said it had detected "an external actor using offensive agentic techniques" and that some non-sensitive data (user IDs, full names, email addresses and organization role labels) was exposed, with no evidence of access to investigation content, authentication credentials or session tokens. The Record noted that Chainalysis did not explain the term or say explicitly that an AI agent caused the breach.1,3,4
Later findings widened the scope. On 2026-11-02 Chainalysis discovered a database compromise exposing user account information. On 2026-11-03 it found that an on-path attack had exposed some user passwords. On 2026-11-04 it said "names, usernames, password hashes and live tokens for all Chainalysis users" had been exposed, and that some KYT accounts appeared to have been accessed without authorization. That reverses its 2026-10-30 statement on tokens.1,2
Who is affected
Every Chainalysis user had names, usernames, password hashes and live tokens exposed, according to the company. Chainalysis says it serves more than 1,500 customers across law enforcement, cryptocurrency and traditional finance, regulators and national security, The Record reported. No affected customer has been named, and the company has not said how many KYT accounts were accessed.1,4
Chainalysis says it has no evidence that investigations data was accessed and no evidence that the actor modified, added or deleted its attribution data.1,2
Who is behind it
No attribution has been made public. Chainalysis describes an external actor and has not said whether the password interception, the hash and token exposure and the KYT account access involved the same attacker or methods, The Record reported. The company says the incident is "not related to the recent crypto theft at Binance."1,3,4
Financial and operational impact
No financial figure has been disclosed. Operationally, Chainalysis took Reactor and Data Solutions offline on 2026-11-02 and, after "abnormal activity", took KYT (user interface and API), Address Screening and its login page offline on 2026-11-04. Chain (Beta) was also offline. For customers that rely on KYT and Address Screening for transaction monitoring and sanctions screening, those products were unavailable from 2026-11-04 until phased restoration began on 2026-11-06.1,2,4
Every user must reset passwords and rotate API keys, and customers had to submit trusted IP addresses for an allowlist before regaining access. Chainalysis also revoked existing customer API keys when it reset its shared user-management and authentication system.1,2
Response and recovery
Chainalysis engaged third-party incident response and forensic support on 2026-10-22, an additional firm on 2026-10-24, and notified law enforcement on 2026-11-02. It says it removed the actor's connection, blocked known IP addresses, closed the exposed Data Solutions API endpoint and interfaces, and reset the shared authentication system. The Block reported that it was also using large language models for a security review; the company's timeline says it used frontier LLMs for code scanning, forensics and threat hunting.2,3
Reactor, KYT and Address Screening came back online with enhanced security on 2026-11-07, and Data Solutions on 2026-11-10. In its 2026-11-13 update, the company said the incident has been contained and that it has identified no unauthorized access by the actor since 2026-11-04. It says the investigation is ongoing.1,2
What investors and lenders should watch
Chainalysis sits inside the compliance stack of exchanges, financial institutions and government agencies, so the questions for its customers' investors and lenders are which customers' KYT accounts were accessed, what an attacker could see or do with live tokens before they were revoked, and whether any screening gaps arose during the outage. None of these has been answered publicly.1,2,4
Also worth watching: the identity of the third-party vendor whose zero-day was exploited, since other firms may run the same software; any customer litigation or regulatory inquiry, none of which was found in the sources read; and the company's promised further updates.2
What is not known
- The third-party vendor and the zero-day exploited have not been named.
- The number of KYT accounts accessed and which customers are affected have not been disclosed.
- What the actor did with exposed live tokens before revocation has not been disclosed.
- Whether one actor or several were involved, and who, has not been disclosed.
- Whether any customer or regulator has taken action is unknown.
Timeline
Actor begins exploiting a zero-day in a third-party vendor's software, per Chainalysis.2
Data Solutions API endpoint found accessible more broadly than intended; fixed.2
Chainalysis begins disclosing the API exposure to impacted customers.2
Actor using agentic techniques detected exploiting a self-registration workflow; outside incident response engaged.2
Same actor found in an internal system exposed by the zero-day; system taken offline, credentials rotated.2
Database compromise discovered; Reactor and Data Solutions taken offline; law enforcement notified.2
On-path attack exposing some user passwords discovered and contained.2
Unauthorized KYT account access found; KYT, Address Screening and sign-in suspended; exposure of hashes and live tokens for all users disclosed.1,2
Phased restoration of KYT and Address Screening begins.1
Company says incident contained; no unauthorized access since 2026-11-04.2
Video and further coverage
Reading video and press coverage...
Sources
- 1.Chainalysis Security Incident Notice (October 30)Chainalysis, 2026-10-30 · primary
- 2.Security Incident UpdateChainalysis, 2026-11-13 · primary
- 3.Chainalysis says hacker using 'offensive agentic techniques' accessed its customers' names and emailsThe Block, 2026-10-31 · press
- 4.Chainalysis warns all users hit in cyber breach involving 'agentic' techniquesThe Record (Recorded Future News), 2026-11-05 · press
DFX Cyber Desk, "Chainalysis breach exposed password hashes and live tokens for all users," DFX Intelligence, published 2026-11-19, https://dfxintel.com/cyber/reports/chainalysis
DFX Cyber Desk reports state only what the cited sources say. A ransomware group's claim is reported as a claim, losses are reported only as a source states them, and nothing is attributed without a named source. Methodology