Chainalysis Breach Widens to All Users: Credentials and Live Tokens Exposed in Agentic Attack

TL;DR

• what: Chainalysis disclosed that an ongoing agentic cyber attack exposed names, usernames, password hashes and live tokens for all of its users.
• impact: Reactor, Data Solutions, the KYT interface and API, address screening products and the login page were taken offline, and every account now needs a password reset and API key rotation.
• fix: Chainalysis says it has addressed the on-path attack vector and added monitoring, and is restoring KYT and Address Screening only for customers who register trusted IP addresses on an allowlist before resetting passwords and rotating API keys.
• who: Every Chainalysis customer, especially teams whose transaction screening depends on the KYT API, plus anyone who reused a Chainalysis password on other systems.

Chainalysis sells the ability to follow money through blockchains. This week it had to trace a breach through its own systems. On November 6, 2026, the blockchain analysis firm said its ongoing investigation into an agentic cyber attack found that names, usernames, password hashes and live tokens for all users had been exposed. Not some users. All of them.

The company responded by switching off much of its product line. Reactor and Data Solutions went offline. So did the Know Your Transaction (KYT) user interface and API, other address screening products, and the login page itself. For customers whose workflows run through those services, the breach is not an abstract data exposure. It is an outage they did not schedule.

How the scope grew in under a week

The story moved quickly. Less than a week before the latest update, Chainalysis said an external actor had used offensive agentic techniques to get unauthorized access to its systems and internal tools. It then described an "ongoing multi-front cyber attack" and the discovery of an "on-path attack" that exposed a subset of customer passwords. The company said that vector has been addressed and it locked the impacted accounts.

The latest disclosure moves the exposure from a subset to the full user base, and adds live tokens to the list. Chainalysis drew one firm line: "At this time we continue to have no evidence that any investigations data has been accessed or Chainalysis attribution data has been manipulated." For a firm whose value rests on the integrity of its attribution data, that is the sentence customers will read first.

⚠️ Why live tokens change the math — Password hashes need to be cracked before they are useful. Live tokens do not. A valid token can let someone act as a signed-in user or integration without ever knowing a password, which is why Chainalysis is pairing password resets with API key rotation for every user.

The road back runs through an allowlist

Recovery is gated. Chainalysis says it will start by restoring KYT and Address Screening, but only for customers who contact [email protected] or their account team with trusted IP addresses to be added to an allowlist. After that, users can reset passwords and rotate API keys to register transactions again. Reactor and Data Solutions have no restoration date yet. "We are working around the clock to harden our systems and bring Reactor and Data Solutions back online," the company said, adding that it will require additional protections to access accounts.

There is friction in the meantime. Customers who got a password reset email were told that "resetting this password won't be possible right now." The company still encourages users to change any reused credentials on other systems.

Part of a wider wave of AI-driven intrusions

Chainalysis has not named the attacker, but it said the attack was similar to those hitting "many other tech platforms in recent weeks." Chainstack, OpenCode, Warp and WorkOS have all disclosed being targeted by AI-driven attacks, some involving an autonomous penetration testing tool called ARTEX. Chainalysis has not said whether ARTEX was used against it.

Microsoft's analysis of the broader campaign, which it assesses has been running since August 2026, shows what this tooling can do. Agents search public GitHub repositories for exposed secrets, analyze what they find and launch follow-on attacks with little need for a human at the keyboard. In at least one case an agent went from scanning GitHub to exfiltrating data from Azure Key Vault in five minutes. Microsoft said the agent "successfully conducted service principal sign-ins on dozens of associated applications across multiple tenants," going after storage account keys, connection strings, publishing credentials and AKS user credentials, then reaching SharePoint, OneDrive and mailbox items. Sign-ins came from 199.19.77[.]84 and 199.19.77[.]18. The agents showed a repeated focus on credentials for AI services, and Google separately reported a criminal market of "LLM Mixers" reselling stolen enterprise model access.

The RedEye take

Chainalysis made the right call by pulling services offline and widening its disclosure rather than waiting for a cleaner story. A vendor that shuts down its own login page to contain an intruder is putting integrity ahead of uptime, and in compliance tooling that is the correct order.

The bigger lesson is about speed. Microsoft documented five minutes from public secret to vault exfiltration. Most incident response playbooks still assume attackers spend days moving laterally while defenders catch up. Agentic tooling breaks that assumption. The time it takes to reach credentials and tokens has dropped to the length of a meeting, and the scope of a breach can grow faster than the disclosures describing it. Organizations that wait for a vendor's final scope statement before acting are now planning against a timeline attackers no longer follow.

The limit of what is known — Chainalysis has not identified the actor, named the tooling used against it, or explained how the on-path attack was positioned. Links to the wider AI-driven campaign rest on the company's own comparison to other recent incidents.

What defenders should learn

• Treat a vendor's first scope statement as the minimum, not the final number. Chainalysis went from a subset of passwords to every user's credentials and live tokens in under a week, and risk decisions made on day one should assume that kind of growth.
• Tokens and API keys are the real blast radius. A password reset that leaves sessions and integration keys alive closes the front door and leaves the side door open. Vendor notices that mention only passwords deserve a follow-up question about tokens.
• Third-party screening services are operational dependencies, not just software subscriptions. When the KYT API went dark, customers lost the ability to register transactions. Continuity planning has to cover the day a critical vendor turns itself off on purpose.
• Recovery controls need groundwork laid before the incident. Chainalysis is restoring access by IP allowlist, which rewards customers who already know their trusted egress addresses and slows those who have to work them out under pressure.
• Non-human identities are now the primary target. Microsoft's findings center on service principals, OAuth applications and Key Vault secrets, with a clear appetite for AI service credentials. Inventory and ownership of machine identities belongs on the leadership risk register, not only in an engineering backlog.

Chainalysis says it will keep communicating as access returns. Customers should watch for the additional account protections the company has promised, and for any change to its statement that investigations and attribution data were untouched. Source: The Hacker News, Ravie Lakshmanan, November 6, 2026, https://thehackernews.com/2026/11/chainalysis-breach-exposes-all-users.html

Originally published on RedEye Threat Intelligence.