aceEmerging evidence
Published recordCrimeProblem Space
More
Chainalysis Security Incident Information
- Truvace record
- TRV-2026-2869raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- News report
- Sources
- 1 sourceJournalism
- sha256
- 8bf59072e8dc…check it
Chainalysis was recently the target of a cybersecurity incident, similar to many other tech platforms in recent weeks. Based on the investigation to date, we have found no evidence of unauthorized access to investigation content, authentica…
The problem
In a breach Chainalysis disclosed on 30 October 2026, an external actor using offensive agentic techniques accessed internal systems; by 4 November names, usernames, password hashes and live tokens for all users were exposed, and products were pulled offline for days.
What this doesn’t fix
Chainalysis's account is a company statement of what its own investigation had found to date, and its early assurances on exposed data were later widened, so the full extent of the breach is not independently verified.
Sources
1 on file- Chainalysischainalysis.com
Cite this record
v1Truvace Impact Record TRV-2026-2869, v1: “Chainalysis Security Incident Information.” Truvace, 2026-11-12. /record/TRV-2026-2869 (accessed on the day you copy it). sha256 8bf59072e8dc5ad5…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2869 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.