On Friday 30 October 2026 Chainalysis said an outside attacker had used "offensive agentic techniques" to get into its systems and internal tools, and that what was exposed was non-sensitive: user IDs, names, email addresses and role labels. It listed what it had no indication of: investigation content, query results, clear-text passwords, MFA secrets and "user session tokens". Five days later its own update said names, usernames, password hashes and "live tokens" for every Chainalysis user had been exposed, its login page and transaction screening were offline, and customers could only get back in from allowlisted IP addresses.

Chainalysis is the blockchain analytics company exchanges use to screen deposits and withdrawals and that police and regulators use to trace stolen funds. When its screening went dark, at least one exchange's withdrawals went dark with it.

[INFO]
Primary source: Chainalysis' own incident page, which keeps every update with its time (30 October to 6 November 2026, read 7 November). Press: BleepingComputer (6 November). Exchange impact: Coincheck's notice as reported by Cryptopolitan (5 November); ICONOMI only through secondary crypto-news flashes. Chainalysis has not said how the attacker got in, how many accounts were misused, or who it was.
◈ interactive artifact
Six Updates, One Week
Chainalysis' status page as a customer watched it, update by update: the banner, the component lights, the exposed list growing from contact details to live tokens, and an exchange's withdrawals stopping beside it.

//How the Disclosure Widened

The incident page is unusually complete; every update stays on it with a timestamp. Read in order:

30 October. Unauthorised access by an external actor using "offensive agentic techniques". Exposed: user IDs, full names, email addresses, organisation role labels. Advice: watch for unexpected reset requests and turn on two-factor authentication.
2 November. "Ongoing cyber threats". Reactor, the investigations product, and Data Solutions taken offline as a precaution; compliance transaction monitoring stays up under watch.
4 November, 09:50 EST. An "ongoing multifront cyberattack". Passwords for a subset of customers were exposed through an "on-path attack", now contained; those accounts are locked. Reset through the normal login page, not email links.
4 November, 10:30 EST. Abnormal activity in the transaction screening products. KYT (interface and API), other address screening products and the login page go offline. Password resets are not possible.
4 November, 23:00 EST. On Monday 2 November Chainalysis found data exposed to a malicious actor: names, usernames, password hashes and live tokens for all users. Some customers' KYT accounts appear to have been accessed without authorisation and are being contacted. No evidence investigations data was accessed or attribution data changed. Access will come back only from trusted IP addresses.
6 November, 03:30 EST. KYT and Address Screening being restored in phases to allowlisted customers, who must reset passwords and rotate API keys before registering transactions. Reactor and Data Solutions: no date.

Two things in that sequence deserve attention. The 30 October notice said there was no indication session tokens were accessed; the 4 November update says live tokens for all users were. And the 23:00 update dates the discovery of the wider exposure to Monday, the same day Reactor was pulled, two days before customers were told. Neither is unusual in a running incident. Both are reasons to treat any "non-sensitive" first notice as a floor.

//A Token Is Not a Password

A password hash still has to be cracked. A live token is already a logged-in session or a working API credential: whoever holds it does not need the password, and resetting the password does not necessarily end the session. That is the likely reason the recovery is built the way it is. Chainalysis did not just ask for resets; it took the login page and the APIs off the internet, and lets customers back only from IP addresses they register, then makes them reset passwords and rotate API keys. A stolen token replayed from anywhere else hits the allowlist first. This is our reading; Chainalysis has not explained its reasoning.

"On-path" is the current term for what used to be called man-in-the-middle: the attacker sits between the user and the service and sees what passes. Chainalysis has not said where on the path. It is a different mechanism from reading a database of hashes, which is why the page reports two separate exposures, a subset of plaintext passwords and every user's hash.

"Offensive agentic techniques" is the only description of the attacker's method. It suggests AI-driven tooling, but nothing on the page says what the tooling did. It is not evidence of anything novel until Chainalysis says more.

//When the Screen Fails Closed

Exchanges screen deposits and withdrawals against analytics services to catch funds from sanctioned or stolen sources. If the screen is unavailable, an exchange has two choices: let transactions through unscreened, or stop. Coincheck stopped. It said an external on-chain analytics service it uses to review transactions failed from about 00:04 JST on 5 November, which is 10:04 EST on 4 November. Withdrawal requests were cancelled and the funds returned to balances; deposits were delayed. Coincheck said there was no unauthorised access to its own platform and did not name the provider.

Chainalysis' update that took KYT and address screening offline is timed 10:30 EST that day, 26 minutes later. The timing fits, and press coverage links the two, but neither company has confirmed it. ICONOMI was reported to have suspended withdrawals citing Chainalysis; we have seen that only in secondary news flashes.

Failing closed is the right default for a compliance control. The lesson is about concentration: a single screening provider is a dependency in the withdrawal path, and its incident becomes yours. Exchanges that had a second provider, or a defined degraded mode, had options Coincheck's notice does not describe.

//Why the Target Matters

Chainalysis holds attribution data, the mapping of addresses to services, groups and cases, that the industry and law enforcement rely on. Chainalysis says it has no evidence investigation data was accessed or attribution data manipulated. That claim deserves the same weight as its first notice: it is what has been found so far. Reactor and Data Solutions, the products closest to that data, are the ones still offline with no restoration date. For context on what that data is used for, see this site's Binance theft write-up, which relies on blockchain analytics firms for every number. Chainalysis has said its incident is unrelated to Binance.

//What Defenders Can Take From It

If you are a Chainalysis customer: reset from the login page, not from an email; rotate every API key; change the password anywhere it was reused; register the narrowest IP allowlist that works; and check KYT activity for transactions or changes your team did not make.
Revoke sessions, not just passwords. When tokens are exposed, a reset that leaves existing sessions valid fixes nothing. Know how to invalidate every token you have issued, and practise it.
Know what fails when a vendor goes dark. Screening, identity, payments: list the providers on your critical path and decide in advance whether each fails open or closed, and for how long.
Read first notices as a floor. The scope here widened from role labels to live tokens in five days.

[IOC]
Organisation: Chainalysis (blockchain analytics); first notice 30 October 2026; latest read 6 November 03:30 EST
Exposed (per Chainalysis): user IDs, names, emails, role labels (30 Oct); passwords for a subset via an on-path attack (4 Nov); usernames, password hashes and live tokens for all users (4 Nov 23:00); unauthorised access to some KYT accounts
Not found (per Chainalysis): access to investigations data; manipulation of attribution data
Offline: Reactor and Data Solutions (from 2 Nov, no return date); KYT UI and API, address screening, login page, Chain (Beta) (from 4 Nov; KYT and Address Screening returning in phases from 6 Nov)
Customer actions: IP allowlist via support@chainalysis.com or account team; password reset; API key rotation
Downstream: Coincheck withdrawals halted from 00:04 JST 5 Nov (provider not named); ICONOMI reported (secondary)

//Sourcing and Uncertainty

Every update, quote, timestamp, service status and customer instruction is from Chainalysis' incident page, read on 7 November 2026. BleepingComputer's 6 November report was used for its reading of "on-path" as man-in-the-middle. Coincheck's times and actions are from Cryptopolitan's report of its notice; the EST conversion is ours (US Eastern was on standard time after 1 November). The ICONOMI suspension appears only in KuCoin news flashes repeating posts on X and is flagged as unconfirmed. The readings of the token risk, the allowlist and the concentration point are ours.

What is unknown. How the attacker got in; what "agentic" means here; where the on-path position was; how many users and KYT accounts were affected; whether any screening result was altered; and when Reactor returns.