Chainalysis security incident notice: an external actor using offensive agentic techniques gained unauthorized access to Chainalysis systems and internal tools (October 2026, updated 7 November)
Chainalysis's incident notice says that in October 2026 it detected an external actor using offensive agentic techniques to gain unauthorized access to its systems and internal tools, that non-sensitive customer data such as user IDs, full names, email addresses and organization role labels were accessed, and, in its 4 November updates, that an on-path attack exposed a subset of customer passwords, which it says has been contained, and that names, usernames, password hashes and live tokens for all Chainalysis users were exposed to a malicious actor.
The record
- Kind
- Disclosure
- Source record
- Chainalysis security incident notice: an external actor using offensive agentic techniques gained unauthorized access to Chainalysis systems (Company statement)
- Record published
- 2026-10-30
- Posted here
- 2026-11-08
- World
- Software agents · Enterprise work agents
- Controls concerned
- none tagged
- Checked
- Checked against its record on 2026-11-08 by a reader who did not draft it; report
verification/reports/SIG-2026-11-08-003-2026-11-08.md.
A signal's controls are the ones its record points at, the exposure; a case's controls are the ones its records show were absent or failed, so the two can differ.
Corrections
Changes to what this signal says, with the reason. Every earlier version is kept.
- 2026-11-08: Summary. the notice's 4 November 11:00 P.M. update says 'names, usernames, password hashes and live tokens for all Chainalysis users were exposed to a malicious actor'; without it the summary gave the 30 October 'non-sensitive' account as the extent of exposure
Show the change
Before: Chainalysis's incident notice says that in October 2026 it detected an external actor using offensive agentic techniques to gain unauthorized access to its systems and internal tools, that non-sensitive customer data such as user IDs, full names, email addresses and organization role labels were accessed, and, in its 4 November update, that an on-path attack exposed a subset of customer passwords, which it says has been contained.After: Chainalysis's incident notice says that in October 2026 it detected an external actor using offensive agentic techniques to gain unauthorized access to its systems and internal tools, that non-sensitive customer data such as user IDs, full names, email addresses and organization role labels were accessed, and, in its 4 November updates, that an on-path attack exposed a subset of customer passwords, which it says has been contained, and that names, usernames, password hashes and live tokens for all Chainalysis users were exposed to a malicious actor.
What a signal is. A signal records what a primary record says; it assigns no fault. It is lighter than a case: one dated item from one record, tagged with the world, sector and controls it touches. It becomes a case when it meets the bar for one.
New signals like this, once a week. A short email when a case, signal or rule touches software agents. Free; unsubscribe in one click.
Get the weekly emailNewer: CVE-2026-120338: Prefab UI's Generative UI sandbox for untrusted code, including code written by a large language model, let that code read and write files on the server
Older: CVE-2026-61789: DBHub, a database Model Context Protocol (MCP) server, lets SQL that hides a write behind a double dash pass its read-only check on MySQL and MariaDB