Eclipse Attack
Pronunciation: ih-KLIHPS uh-TAK
Definition
Eclipse Attack is an attack or weakness pattern that isolates a blockchain node from honest peers so an attacker can control the network information that node receives. Eclipse Attack must be evaluated through its prerequisites, entry point, affected asset or trust boundary, attacker capability, observable indicators, and possible financial or operational impact.
Overview
Meaning and scope
Eclipse Attack is an attack or weakness pattern that isolates a blockchain node from honest peers so an attacker can control the network information that node receives. Eclipse Attack must be evaluated through its prerequisites, entry point, affected asset or trust boundary, attacker capability, observable indicators, and possible financial or operational impact.
How it works
An eclipse attack surrounds a target node with attacker-controlled peers, preventing or delaying connections to honest participants. The isolated node receives a distorted view of transactions, blocks, chain tips, fees, or network activity while believing it remains normally connected. Attackers may exploit predictable peer selection, address-table poisoning, excessive inbound connections, network routing weaknesses, or repeated restarts. Isolation can support double-spend attempts, selfish mining, transaction censorship, delayed settlement, or deception of services that rely on one node. Defenses include diversified peer selection, protected seed sources, limits by network range, persistent trusted peers, authenticated connections where available, and monitoring for abnormal topology or chain divergence.
Practical payment example
A payment operator’s node sees a transaction that other peers do not. The system cross-checks block and mempool observations before releasing a high-value order.
Operational checks
An eclipse attack isolates a node by influencing its peer connections and feeds it a restricted view of network information. Monitoring several independent sources reduces single-view risk. Critical payment systems should compare independent nodes and external network observations. For Eclipse Attack, an indicator supplies evidence, a control changes exposure, a policy states expectations, and an incident records an event; using those labels interchangeably obscures decisions.
Distinctions and limits
Eclipse attacks target network visibility, whereas chain reorganizations concern competing accepted histories. Either can affect what a single watcher believes. A node can follow valid protocol rules yet remain dangerously misinformed when attackers control all of its network connections. Assessment of Eclipse Attack should trace an attack or weakness pattern that isolates a blockchain node from honest peers so an attacker can control the network information that node receives from prerequisite and entry point through observable impact on the affected service.
Related reading
Related reading: network activity, network routing.
Example
A payment operator’s node sees a transaction that other peers do not. The system cross-checks block and mempool observations before releasing a high-value order.
Comparison
Eclipse attacks target network visibility, whereas chain reorganizations concern competing accepted histories. Either can affect what a single watcher believes.
Key Takeaway
Do not depend on one unverified network vantage point for high-stakes settlement.
Sources
- NIST Documentation: Cyberframework — NIST (2026-07-30)
- FATF Documentation: Virtual Assets — FATF (2026-07-30)