v1 → v2
Scores
trust_score22 → 21
severity_base— → —
score_modifier-6 → -1.4
Sections
Incident Overview
unchanged
Attack Vector and Methodology
unchanged
Funds Lost and Chains Affected
unchanged
Client Fund Segregation and Solvency
unchanged
Disclosure Timeline and Transparency Concerns
unchanged
Regulatory and Law Enforcement Response
unchanged
Broader Security Context
unchanged
Timeline events
No timeline changes.
Accepted submissions
+ addedurlincriminating
{"url":"https://www.cryptotimes.io/2026/07/27/triple-a-hack-losses-reach-11-8m-as-deposits-drained-for-31-hours/","note":"Post-incident reporting reveals Triple-A's $11.8M treasury hack on July 27, 2026 included deposits continuing to flow into compromised wallets for 31 hours after initial outflows began — indicating the team was unaware the wallets were live and drained. The Singapore Police Force investigation is ac","title":""}Each version is bound to the decision event that created it. Verify the chain anchor for either via the audit log.
v1 hash: 24358015dea350fe44bf2dfa61050fba72665d6d2f8c85574951d3adceb38b48
v2 hash: 8GkF4B3Kb5cK1CN2BR4Seo72sKwniECuVRCXgLXZzaMc