News

Malware Can Use Blockchains Without Hacking the Network

Chainalysis describes blockchain dead drops that redirect malware toward attackers.

Category byline: Dylan Foster Updated October 5, 2026 2 min read

Prepared automatically from the linked sources. The category byline does not confirm personal authorship or review. Editorial policy.

Illustrative photograph: Person using a laptop in a dark workspace; illustrative of malware research, not the investigated operation
Illustrative photograph. Photo by Sora Shimazaki. Pexels. Pexels License.

Chainalysis’s September 17 research describes public blockchains serving as persistent meeting points between malware and its operators. The firm calls them blockchain dead drops: transactions or smart contracts hold payloads, configuration data or pointers that infected devices retrieve. Its report emphasizes campaign durability, rather than greater destructive power. An attacker can retain a coordination layer when conventional domains, hosting or repositories are removed. The actual attack activity can then continue outside the blockchain after malware retrieves the information it needs. Chainalysis.

Editorial analysis: The ledger’s role here is to publish directions, not necessarily to be the system under attack. That distinction separates a blockchain interaction from a blockchain breach. It does not rule out cryptocurrency theft: Chainalysis describes both wallet-targeting information stealers and remote access trojans. The important question is what the malware retrieves and subsequently does on a device. A durable public record can support hostile coordination without making every use of that network hostile. Chainalysis.

Read-only retrieval

Google Threat Intelligence Group’s October 2025 report provides an earlier example. It said North Korean actor UNC5342 had incorporated EtherHiding into a social engineering campaign since February that year. Fake interviews and other lures helped initiate compromise; blockchain infrastructure supported malware delivery. The campaign targeted developers in technology and cryptocurrency sectors. The report discussed ClearFake, which used deceptive browser update prompts. These are historical cases illustrating the mechanism, rather than newly disclosed incidents from Chainalysis’s September report. Google’s 2025 report.

Google described a loader retrieving malicious material through a read-only blockchain call, such as eth_call. That retrieval did not require creating a transaction or paying a transaction fee. Editorial analysis: A blockchain can therefore participate in malware delivery even when the retrieval leaves no transaction history on the chain. Counting transactions alone would not show each retrieval described in this model.

The report distinguishes the lure, loader, retrieval and execution stages, making clear that the blockchain’s availability and the victim’s execution of malicious code are separate parts of the attack. Google’s 2025 report.

The resolver distinction

MITRE’s Dead Drop Resolver entry, T1102.001, defines the broader pattern. Attackers place information on a legitimate external service that points infected devices toward additional command-and-control infrastructure. The stored content may contain encoded domains or IP addresses. MITRE describes examples involving ordinary websites, forums and repositories as well as blockchain systems. Its examples include GitHub and YouTube. The resolver is an intermediate source of directions, so it need not be the final server communicating with the malware. MITRE.

The entry explains that this arrangement can conceal backend infrastructure from analysis of a malware binary while letting operators change that infrastructure dynamically. Editorial analysis: Removing an identified destination and removing the place that advertises its replacement are different interventions. This helps explain why a dead drop can outlast a particular server.

The classification also prevents a misleading shortcut: observing blockchain use does not by itself describe the initial infection or establish a network vulnerability. The relevant sequence begins with infected software consulting a resolver and then reaching the additional infrastructure it identifies. MITRE.

Sources