Urgent.News

What's breaking now, across thousands of outlets.

Tech

The Chainalysis Breach: From "No Credentials Accessed" to "All Users Exposed" in Five Days

On October 30, 2026, Chainalysis told its customers it had been the target of a cybersecurity incident - and that it had "found no evidence of unauthorized access to investigation content, authentication credentials, or session tokens." Five days later, on November 4, the company updated the same blog post with a very different sentence: "certain customer information including names, usernames,…

On October 30, 2026, cybersecurity firm Chainalysis notified its customers about a potential cybersecurity incident, assuring them that no evidence of unauthorized access to investigation content, authentication credentials, or session tokens had been found. However, just five days later, on November 4, the company revealed that certain customer information, including names, usernames, password hashes, and live tokens for all Chainalysis users, had been exposed to a malicious actor.

Chainalysis, a leading blockchain-intelligence company with over 1,500 customers including law enforcement, regulators, national security agencies, banks, and crypto exchanges, uses its tools to trace transactions and screen them for money laundering. The implications of such a breach are not only reputational but also operational, as any company affected can disrupt critical services.

The timeline of the incident unfolded gradually. Initially, Chainalysis disclosed the unauthorized access on October 30, revealing that an external actor had gained unauthorized access to internal systems and tools using offensive agentic techniques. Some non-sensitive data, such as user IDs, full names, email addresses, and organization role labels, was accessed, but no evidence of access to credentials or tokens was found at that time.

As the investigation progressed, Chainalysis decided to take its Reactor investigations tool and Data Solutions offline out of caution on November 2. They kept their compliance transaction-monitoring products running, emphasizing their importance in detecting money laundering across the ecosystem.

The company notified a subset of customers on November 4 that their passwords had been exposed in what Chainalysis called an on-path attack, an interception of communications between users and the service. Affected accounts were locked, and users were forced to reset their passwords. However, just forty minutes later, abnormal activity led to the offline shutdown of the KYT user interface and API, other address-screening products, and the login page itself.

Customers were then informed that resetting their passwords was not currently possible and were advised to reset reused passwords on other services instead.

On November 4 night, the company revised the scope of the breach, revealing that names, usernames, password hashes, and live tokens for all Chainalysis users had been exposed. They added that there was no evidence that investigation data was accessed or that its attribution data was manipulated, although some customers' KYT accounts appeared to have been accessed without authorization.

The implications of password hashes and live tokens being exposed are significant. Password hashes, while not passwords themselves, can still be vulnerable to attacks if the hashing algorithm used is weak or unsalted. Live tokens, on the other hand, provide unauthorized access to user sessions or APIs, posing a serious security risk.

Chainalysis has not explicitly confirmed the use of AI agents in the breach, only referring to offensive agentic techniques. The company has also not disclosed whether the interception of passwords, exposure of hashes and tokens, and unauthorized KYT account access were carried out by the same attacker, using the same method, or within the same timeframe.

To maintain security, Chainalysis customers are advised to submit trusted IPs to the allowlist, reset their passwords, rotate their API keys, enable two-factor authentication if not already, and change passwords if reused. This incident highlights the importance of transparency in cybersecurity incident disclosure and the need for customers to remain vigilant in safeguarding their accounts.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The hardest websites to scrape in 2026: what the benchmarks show

Disclosure: I'm a co-founder of ScrapeUnblocker, one of the APIs measured below. Every number here has a public source you can check. A lot of websites are still simple to scrape.

  • Shein, G2, and Hyatt identified as hardest websites to scrape in 2026
  • Success rates of 21.88%, 36.63%, and 43.75% for these sites
  • Established scraping API providers face challenges with protected targets

RAG Pipeline Utils v3.8: Testing RAG Answers in TypeScript

v3.8.0 is about testing RAG in TypeScript. The answer matchers now compile with types, and a new guide walks through the whole setup with Vitest, from a unit test to a test set that fails CI when answers get worse. Nothing breaks for existing code.

  • RAG Pipeline Utils 3.8 introduces TypeScript support for testing RAG answers.
  • New matchers toBeGroundedIn, toCite, and toContainNoPII enable early error detection.
  • Guide provides step-by-step setup using Vitest for unit, answer, and evaluation tests.

More from Friday 6 November →