Chainalysis customer-profile data incident

Names, emails, user IDs and role labels were accessed; sensitive investigation data was not known to be affected.

Last modified

Summary

  • Environment: Chainalysis internal systems and tools
  • Operational impact: No service interruption established in the public notice
  • Financial impact: No confirmed incident cost quantified
  • Record status: Developing record. Reviewed October 31, 2026; updated as evidence emerges.

What happened

Chainalysis detected an external actor accessing internal systems during October 2026. Its October 30 disclosure confirmed access to customer profile information. [1]

Impact

Accessed fields included user IDs, names, email addresses and organization-role labels. The affected-record total remained under investigation. Chainalysis had no indication of access to investigation cases, graphs or notes, transaction/query results, cleartext passwords, MFA secrets or session tokens. [1]

Timeline

  1. Profile-data access disclosed

    The security notice describes confirmed fields and the continuing scope assessment.

    [1]
  2. Briefing updated

    This briefing was last reviewed and updated on October 31, 2026.

Threat Group & Attack Vector

Chainalysis described the use of offensive agentic techniques, but did not establish the precise exploit path or actor identity. It explicitly separated this incident from the reported Binance theft. [1]

Actors

  • No threat actor group has been identified in the reviewed public evidence.

TTPs

  • No specific MITRE ATT&CK technique is currently mapped for this case.

Response

The company patched vulnerabilities, notified all customers and engaged outside experts. It recommended two-factor authentication and caution about targeted phishing. [1]