Skip to main content
All incident reports
Incident report

Chainalysis breach exposes credentials and live tokens for all users

Chainalysis says an external actor used what it calls offensive agentic techniques to reach its internal systems and tools, and later found that names, usernames, password hashes and live tokens for all of its users had been exposed. The blockchain analytics firm has taken several products and its login page offline while it investigates.

· First published

The short version

  • The breach. Chainalysis detected an external actor in its systems and internal tools in October, using what the company calls offensive agentic techniques. It disclosed the incident on 30 October and has not said which vulnerabilities or internal tools were involved, or how long the attacker had access.
  • Wider exposure. In an update on 4 November, Chainalysis said names, usernames, password hashes and live tokens for all users had been exposed to a malicious actor. Its first disclosure had described only user IDs, full names, email addresses and organisational role labels, and said there was no evidence credentials or session tokens were taken.
  • Interception of passwords. Some customers' passwords were exposed in an on-path attack, also known as a man-in-the-middle attack, which Chainalysis says it contained and remediated, locking the affected accounts. The company has not said whether that interception, the exposure of hashes and tokens, and suspected access to some KYT accounts involved the same attacker or methods.
  • Services offline. Chainalysis took Reactor, Data Solutions, the Know Your Transaction (KYT) user interface and API, address-screening products and its login page offline. It planned to start restoring KYT and Address Screening on 5 November for customers that supplied trusted IP addresses for an allowlist.
  • What the firm says is untouched. Chainalysis says it has no evidence that investigation content, transaction or query results were compromised, or that attribution data was manipulated, and that the incident is unrelated to the recent Binance theft.

Timeline

DateEvent
OctoberChainalysis detects an external actor using offensive agentic techniques in its systems and internal tools.
30 OctoberChainalysis discloses the incident, saying names, email addresses, user IDs and role labels were accessed and that it found no evidence credentials or session tokens were exposed.
2 NovemberChainalysis takes Reactor and Data Solutions offline as a precaution and establishes that names, usernames, password hashes and live tokens for all users were exposed.
4 NovemberAn updated disclosure is posted; later that night abnormal activity prompts Chainalysis to take KYT, other address-screening products and the login page offline.
5 NovemberChainalysis plans to begin restoring KYT and Address Screening for customers who submitted trusted IP addresses.

How the incident unfolded

Chainalysis says it detected an external actor in its systems and internal tools in October, using what it described as offensive agentic techniques. It published its first disclosure on 30 October and told customers that user IDs, full names, email addresses and organisational role labels had been accessed, with no evidence that investigation content, credentials or session tokens were taken.

By 2 November the picture had changed. Chainalysis found that names, usernames, password hashes and live tokens for all users had been exposed, and said some customers' passwords had been exposed in an on-path attack, in which an attacker intercepts traffic between users and a service. The company says it contained that interception and locked the affected accounts.

On 4 November, forty minutes after telling customers to reset passwords, Chainalysis took KYT, other address-screening products and its login page offline, so the resets could not be done immediately. Reactor and Data Solutions had already been taken offline on 2 November. The company says access will require every user to reset their password and rotate API keys as appropriate.

Who is affected

Chainalysis says the exposure covers users provisioned on its platform across customer organisations, and it is still working out which records belong to which organisation. Its website says it serves more than 1,500 customers in law enforcement, national security, regulators, cryptocurrency businesses and mainstream finance; the company has not said how many individual users it has.

The company says it has no evidence that investigation content, transaction or query results, or passwords in clear text were compromised, or that attribution data was manipulated. It also says some customers' KYT accounts appeared to have been accessed, without saying how many or what was done in them.

What agentic techniques means here

Chainalysis has not explained what it means by offensive agentic techniques or given technical detail on the intrusion. Agentic describes AI systems that carry out multi-step tasks with little human intervention. It is unclear whether the attacker used an existing offensive framework such as ARTEX or custom-built AI agents that find and exploit vulnerabilities and chain further actions.

Microsoft, cited in reporting on the case, says the ARTEX framework is used to search public GitHub repositories for exposed secrets and then run follow-on attacks, and describes one case where an agent moved from scanning to exfiltrating data from Azure Key Vault in five minutes. No source links ARTEX to the Chainalysis intrusion. Chainalysis says it is working with outside experts and using large language models in its security review.

Chainalysis says the incident is not connected to the recent Binance theft, which it describes as separate. It also says it has seen a rise in AI-driven attacks across the industry, and other platforms have disclosed similar activity in recent weeks, though the sources do not establish a common actor.

What is not known yet

  • Who carried out the intrusion, and whether one actor is responsible for the password interception, the exposure of hashes and tokens, and the suspected KYT account access.
  • How many users and customer organisations are affected, and which records belong to each organisation.
  • Which vulnerabilities or internal tools the attacker used, and how long the access lasted before it was detected.
  • What Chainalysis means by live tokens, and whether any of them were used to reach customer accounts.
  • How the exposed password hashes were generated, and how quickly they could be cracked.

What to do

If you use Chainalysis

  1. Contact Chainalysis support or your account team with trusted IP addresses so your users can be added to the allowlist.
  2. Once access is restored, reset your password and rotate API keys before registering transactions.
  3. Turn on multi-factor authentication and reach the login page directly rather than following links in password-reset emails.
  4. Treat unexpected authentication prompts, password-reset requests, and approaches offering fund recovery or recruiting as suspicious.

If you may have reused that password elsewhere

  1. Reset the same password on every other system where you used it, as Chainalysis advises.
  2. Do the same for any API keys or tokens shared between Chainalysis and other services.

For everyone else

  1. Plan for a full credential rotation when a SaaS provider holding your password hashes or active tokens is breached, since hashes can be cracked and live tokens can bypass passwords.
  2. Expect impersonation of the breached vendor in email and messages, and verify through a known channel before acting.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.