Chainalysis now says password hashes and live tokens for all users were exposed
Chainalysis said on November 4 that names, usernames, password hashes and live tokens for all users were exposed, reversing its October 30 statement that no session tokens were accessed. It took KYT, address screening and its login page offline after abnormal activity.
Chainalysis said late on November 4 that customer names, usernames, password hashes and live tokens for all users had been exposed to a malicious actor, reversing its October 30 statement that it had no evidence session tokens were accessed. The blockchain analysis firm first disclosed that an external actor using "offensive agentic techniques" had reached its systems and internal tools, exposing user IDs, names, email addresses and organization role labels. On November 2 it took its Reactor and Data Solutions products offline. On November 4 it said an "on-path attack" had exposed a subset of customer passwords and locked those users out, then took its KYT and address screening products and login page offline after detecting abnormal activity. It is notifying customers whose KYT accounts were accessed, and says it found no evidence that investigations data was accessed or attribution data manipulated.
Why it matters
The live tokens matter more than the hashes. A valid session or API token works without the password or the second factor, so turning on two-factor authentication now does not stop a token already stolen; that is why Chainalysis will require every user to reset passwords and rotate API keys when access returns. The disclosure moved in five days from "no session tokens" to all users' tokens, a reminder that first statements describe what has been checked, not what happened.
If you use Chainalysis, send your trusted IP addresses for its allowlist, reset passwords through the official login page rather than emailed links, rotate API keys, and change any reused password elsewhere. The technique page is token replay, and device-bound session credentials are the control that makes stolen sessions hard to reuse. WorkOS also reported AI-assisted attack tooling this week.
Source: Chainalysis
Related on Start with Identity
- BlogOpenCode Console breach may have exposed users' saved AI provider keys
OpenCode says an intruder reached a legacy system on the night of October 16 and may have exposed OpenAI, Anthropic and Google keys that 1.4% of OpenCode Consol
- BlogChainstack says an attacker reached production through a third-party component and took password hashes
Blockchain infrastructure provider Chainstack says an attacker entered a development environment through a third-party component on October 26, reached producti
- BlogGoogle: LLMjacking starts with stolen cloud identities and has cost some companies $1 million
Google Threat Intelligence Group and Mandiant say LLMjacking intrusions ran up more than $100,000 in fraudulent AI charges in a day and $1 million in total at s
- CVEStrapi query filter leaks password hashes and reset tokens
Strapi let API callers filter users on private fields and read the answer out of the response, leaking password hashes and password reset tokens. Fixed in 4.8.0
- CVECheck Point Security Gateway information disclosure of password hashes
An unauthenticated read on Check Point Security Gateways leaked password hashes, including those used for VPN and local admin. CISA KEV. May 2024. Hash disclosu
- RankingBest CIAM for High Scale: Top 5 Platforms for Millions of Users
The best CIAM platforms for high scale in 2026: Auth0, Ping Identity, MojoAuth, Stytch, and Transmit Security. Ranked for throughput, global reach, spike handli