Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Chain Hopping
Cyber Security

Chain Hopping

← Back to Glossary
By NHI Mgmt Group Updated October 30, 2026 Domain: Cyber Security

A laundering technique that moves assets across multiple blockchains to break forensic continuity. It does not remove visibility, but it makes tracing harder because analysts must correlate activity across different ledgers, services, and operator identities to reconstruct the full path of funds.

How Chain Hopping Works

Chain hopping is a laundering pattern that splits transfers across multiple ledgers so no single blockchain shows the whole path of funds. The goal is not invisibility, but fragmentation: each hop forces investigators to stitch together transactions, timing, bridge activity, and intermediary services before the trail becomes intelligible.

This matters because the technique exploits the fact that blockchain tracing is only as strong as the analyst’s ability to correlate events across ecosystems. When assets move between chains, the investigator must contend with different address formats, bridge mechanics, custodial or non-custodial services, and the possibility that the actor changes wallets or operator identities at each step.

Why Chain Hopping Complicates Investigation

The core difficulty is continuity. A transfer that is obvious on one ledger may become ambiguous after it passes through a bridge, swap service, or exchange deposit address. That does not erase evidence, but it raises the cost of reconstruction and increases the chance that weak attribution assumptions break the case.

Chain hopping also creates analytical blind spots when teams rely too heavily on one chain’s telemetry, one vendor’s clustering model, or one compliance dataset. A complete view usually requires combining on-chain data with off-chain records, such as service logs, withdrawal records, and any available customer or operator context tied to the movement.

Detection and Attribution Challenges

Detection depends on recognising patterns, not just single suspicious transfers. Repeated cross-chain movement, rapid swaps between assets, bridge usage that does not fit normal treasury behaviour, and sudden changes in wallet control can all be indicators that the activity is being structured to frustrate tracing.

Attribution is harder because each hop can introduce a new layer of pseudonymity. Analysts may need to correlate timing, amounts, fee patterns, bridge endpoints, and reuse of infrastructure or services to show that apparently separate transactions are part of one laundering sequence. Frameworks such as MITRE ATT&CK Enterprise Matrix help teams think in terms of multi-step adversary behaviour, even when the technique spans financial rails rather than conventional endpoints.

Investigation and Control Implications

Because chain hopping is designed to obscure continuity, investigators need a workflow that preserves evidence across chains instead of treating each ledger as a separate incident. That includes maintaining a unified timeline, retaining bridge and exchange records, and documenting every assumption used to connect one hop to the next.

Controls matter most at the boundaries. Visibility into bridge interactions, sanctions screening where applicable, wallet clustering, and exchange monitoring can help surface the handoff points where the actor tries to break tracing. For broader control design, the CSA Cloud Controls Matrix is useful as a governance reference for identity, logging, and supply-chain style oversight, while ENISA Threat Landscape provides a useful lens on how organised criminal activity adapts when defenders increase visibility on one part of the path.

Risk and Threat Considerations

Chain hopping creates a material investigation and enforcement risk because it degrades continuity without eliminating evidence. The technique can delay interdiction, complicate seizure decisions, and make it harder to prove control relationships across the full movement of funds.

Failure mechanism: The actor breaks the trail into smaller, cross-ledger segments that must be reassembled from multiple sources, and each added hop increases the chance of attribution error, missed linkage, or delayed response.

Impact: Investigations take longer, tracing confidence falls, and illicit funds have more time to be dispersed, cashed out, or layered through additional services before containment.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKTA0008 — Lateral MovementChain hopping fragments movement across systems and services to impede tracking.
Recommendation — Correlate multi-hop fund movement as a lateral traversal pattern and expand telemetry across each transfer boundary.
CIS Controls v8CIS-8 — Audit Log ManagementTracing chain hopping depends on retaining and correlating logs across ledgers and services.
Recommendation — Preserve and centralise logs from bridges, exchanges, and wallet activity to support cross-chain reconstruction.
NIST SP 800-53 Rev 5AU-6 — Audit Record Review, Analysis, and ReportingChain hopping requires review and correlation of audit evidence across multiple environments.
AC-2 — Account ManagementOperator identity changes and service usage are central to reconstructing chain-hopping activity.
Recommendation — Analyze audit records across all transfer points to reconstruct the full path of funds. Track and govern accounts and service relationships that can be used to move value across chains.

Practitioner Guidance

What to watch for: Treat the first cross-chain transfer as an escalation point, not as the end of the trace. Once assets leave a single ledger, analysts should assume that the adversary is actively optimising for fragmentation and should widen collection to include bridge data, exchange touchpoints, and any associated off-chain records.

Practitioner takeaway: Chain hopping is best handled as a correlation problem, not a chain-specific one; the investigation succeeds when teams preserve continuity across every hop.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org