What happened
Chainalysis initially disclosed the incident on October 30, mentioning an “external actor using offensive agentic techniques” and no evidence of credential access. Around November 2, it preventatively disabled the Reactor investigative tool and Data Solutions product. In a November 4 update, it admitted that all user data had been exposed, some passwords were intercepted in an on-path attack (according to the company, this method was contained), and some KYT accounts were likely accessed without authorization. Approximately 40 minutes after sending this information to clients, the company disabled the KYT interface and API, other address screening products, and the login page due to “unusual activity.”
Chainalysis did not explain what “offensive agentic techniques” mean, did not identify the perpetrator, and did not specify how passwords were hashed or how many users it has. The restoration of KYT and the Address Screening service is planned after collecting lists of trusted IP addresses from clients.
Key findings
- Exposed: names, usernames, password hashes, and active tokens of all users; some passwords intercepted in an on-path attack; suspected unauthorized access to some KYT accounts.
- Disabled: Reactor and Data Solutions (from approx. Nov 2), KYT interface and API, other address screening products, login page, and Chain (Beta).
- Attribution: none; the company mentions “offensive agentic techniques” but does not explicitly confirm that an AI agent led the attack.
- Recommendations for clients: password reset and API key rotation, logging in only by direct website entry (not from email links), reporting trusted IP addresses for an allowlist.