Public nodes are visible
A node must accept outside peers, but probing can also reveal its wallet and management interfaces.
Industry blocklist
Cryptocurrency Infrastructure blocklist
Keep public node connectivity available while tightening the edges around wallet and management services.
The coverage
What our sensors observed
Our sensors saw probes against public blockchain nodes, wallet services, payment channels, and peer networks. The mapping includes services intended for public connections as well as interfaces that may need narrower access.
Why use this feed
A public node needs peers, while a wallet or management interface may need access from only a few clients. Review observed scanner sources at those narrower edges first. If you also use the list on a public peer service, check what the node needs to accept before enforcing blocks. The same IP rule should not be applied blindly to every service in a node deployment.
The challenges
Scanning can reveal a reachable service before an exploit attempt, whether a flaw is known or still undisclosed. Our sensors record sources doing that probing. A firewall rule using the feed can deny a listed source before its next connection reaches your service, without needing to recognize the exploit itself.
Private edges carry risk
If a reachable wallet or administration service has a flaw, later requests may try it after the interface is found.
Do not wait on one node
A listed source can be filtered at a narrow management edge before it reaches that node for the first time.
Edge enforcement
Defend your edge
The feed loads matching rules into your firewall. Listed sources are intercepted before crossing the edge; traffic with no match continues to your services.
Where this feed fits
Use the observed source list where your existing edge controls meet these reachable services.
Check the list against the connections a node must accept. A public peer interface needs different rules from a private administration service.
Apply the feed around a reachable wallet interface. Confirm which clients and operators need access before adding blocks.
Review scanner sources at gateways serving payment channel services. Keep the connections needed by trusted peers available.
Use the list in front of exposed node management interfaces. Limit operator access separately from the peer network.
Where peer services must stay public, review the list against normal network participation before enforcing a deny rule.
Review scanner sources around a reachable distributed content service. Check the peer connections it needs before applying a deny rule.
Industry blocklist
Start blocking observed scanner sources.
Choose this industry, connect the feed to your firewall, and review access with the people who run each service.