Malicious Node + GG20 TSS Key Leak
Treat this as a reported explanation to test against code, traces, transaction data, and other primary evidence.
Preparing your view
Checking the session, access policy, and current workspace data.
Checking the session, access policy, and current workspace data.
Malicious Node + GG20 TSS Key Leak
Malicious THORChain node progressively leaked GG20 TSS key material; unapplied patch led to $10.7M drain.
Imported-record overview
These fields reproduce or normalize claims in an imported research record. “Reported” describes provenance; it does not mean ChainRadar has confirmed the claim.
Treat this as a reported explanation to test against code, traces, transaction data, and other primary evidence.
Date-free learning path
Synthetic study sequence for learning purposes; timestamps and ordering may not reproduce the full verified incident chronology. Synthetic dates are deliberately omitted below.
STUDY PHASE
Node.joinValidatorSet()STUDY PHASE
TSS.signingRound(leak_shares)STUDY PHASE
TSS.reconstructKey()STUDY PHASE
Vault.outboundTransfer($10.7M)STUDY PHASE
Network.halt()Teaching model
Educational reconstruction intended to explain the reported attack pattern, not a transaction-level evidentiary trace.
Start at Stage 1 and follow the numbered arrows. Every label is derived from the imported flow actions and structure.
Values describe reported movement between stages. Repeated amounts are not additional losses.
| Step | From | To | Reported action | Value |
|---|---|---|---|---|
| 01 | Key Reconstruction | THORChain system | Key Reconstruction | $10.70M |
| 02 | THORChain system | Signed Outbound | Signed Outbound | $10.70M |
| 03 | Signed Outbound | Value destination | Drain | $10.70M |
Imported indicators
Contract entries are reproduced from the local research archive. Confirm chain, bytecode, ownership, and incident relevance against primary evidence before using them in an investigation.
The absence of an address in this record does not establish that no contract was involved.
Defensive prompts
These imported mitigation labels are study prompts, not a complete or validated remediation plan. Test them against the protocol's actual architecture and failure mode.
Investigator workflow
Turn this background study into questions for a separate, evidence-led investigation. Never promote an educational edge or imported label into a finding without corroboration.
Preserve official disclosures, on-chain transactions, code, retrieval times, and other evidence supporting each material claim.
Start from corroborated addresses or transactions and trace each hop without assuming the educational flow is exact.
Compare decoded calls, logs, bytecode, and state changes with the reported cause.
Record provenance for every claim and identify gaps that still require confirmation.
Source status: cataloged. Classification: educational. Risk methodology: heuristic only. Primary-source verification remains required for every material claim.