Opens in a new tab

Blockchain Dead Drops Reshape Malware C2

Emerging malware C2 uses public blockchains to evade takedowns

Blockchain dead drops are giving malware operators a resilient way to publish command-and-control instructions. On 18 November 2026, Cisco Talos detailed how attackers can retrieve encrypted configurations or server pointers from public ledgers instead of relying on a fixed domain.

The technique turns widely accessible blockchain infrastructure into a directory for malware. Because defenders cannot remove a public transaction or easily disable a decentralised network, taking down the attacker’s current server may only cause infected systems to query the ledger and locate its replacement.

How blockchain dead drops support resilient C2

Traditional command-and-control, or C2, commonly depends on hardcoded domains and IP addresses. Once identified, those assets can be blocked, suspended, seized or redirected to a defensive sinkhole. This creates a critical point of failure for the attacker.

Cisco Talos describes an alternative model in which the blockchain does not necessarily carry the attacker’s full malicious payload. Instead, a transaction, wallet, smart contract or memo acts as a dead drop containing an encrypted configuration, domain, IP address or reference to another location.

Malware can retrieve that information through a read-only remote procedure call, often using JSON-RPC. These requests may travel to legitimate public gateways and blockchain nodes, making them harder to distinguish from authorised cryptocurrency, Web3 or development activity.

The retrieved configuration can remain in process memory rather than being written to disk. The malware then decrypts or parses the information, contacts the current C2 server and begins beaconing or downloads another payload. An operator can update the on-chain pointer when infrastructure is blocked, without reinstalling the malware on compromised devices.

Talos identifies several channels associated with blockchain dead drops:

  • Bitcoin transactions carrying data that can be decoded into backup C2 information.
  • EVM-compatible smart contracts queried through methods such as eth_call.
  • TRON wallets used as a source of operational information.
  • Solana transaction memo fields containing C2 pointers.

The specific TRON element has not received the same level of independent, primary-source technical documentation as the examples involving Bitcoin, BNB Smart Chain, TON and Solana. It should therefore be treated as an emerging Talos finding rather than a broadly corroborated pattern.

Confirmed blockchain dead drops in active campaigns

Glupteba and Bitcoin transactions

Glupteba provides one of the earliest publicly documented examples. On 4 September 2019, Trend Micro reported that the Windows-focused botnet could obtain backup C2 information from Bitcoin transactions. Google confirmed the blockchain fallback when it disrupted Glupteba on 7 December 2021.

The malware contains hardcoded Bitcoin wallet addresses. If its normal HTTPS infrastructure becomes unavailable, it can inspect blockchain data through Electrum services or public interfaces, locate data in an OP_RETURN field and decrypt the embedded domain. Documented implementations used AES-256-GCM, with the required key hardcoded in the malware and the initialisation vector carried in the transaction.

Addresses connected with this fallback included 1CgPCp3E9399ZFodMnTSSvaf5TpGiym2N1, 15y7dskU5TqNHXRtu5wzBpXdY5mT4RZNC6 and 1CUhaTe3AiP9Tdr4B6wedoe9vNsymLiD97. This mechanism allowed surviving infections to reconnect after conventional domains were suspended or sinkholed.

EtherHiding on BNB Smart Chain

EtherHiding applied the same principle to EVM-compatible smart contracts. Between 13 and 17 October 2023, researchers documented ClearFake campaigns using BNB Smart Chain contracts to distribute changing malicious code and C2 references.

Injected website scripts loaded a blockchain JavaScript library and issued an eth_call request to an attacker-controlled contract. The response contained hex or base64-encoded JavaScript or configuration data. Once decoded in the browser, it directed the victim towards the next attack stage, including deceptive browser update prompts and payload delivery.

Changing the contract data allowed operators to replace delivery infrastructure without modifying every compromised website. Related enterprise telemetry published on 30 January 2026 included connections to bsc-dataseed.binance[.]org and bsc-testnet.drpc[.]org, demonstrating why legitimate blockchain endpoints require contextual monitoring rather than simple reputation checks.

TONResolver and an updateable smart contract

Trend Micro documented TONResolver on 29 June 2026 after phishing activity targeting Japanese hospitality partners during May and June 2026. The Windows infection chain installed a Node.js backdoor and downloaded Node.js v24.13.0 to support persistence and execution.

The backdoor contacted tonapi[.]io and invoked a smart contract getter named methods/get_domain. The active C2 domain was stored in the contract’s data cell. An authorised management wallet could send an internal message to update that value, allowing the attacker to rotate infrastructure while the infected client continued consulting the same contract.

The analysis covered the TON Virtual Machine assembly, Bag of Cells layout, operation code and CRC16-derived method selector. This was operational malware rather than an academic proof of concept.

GlassWorm and Solana memo fields

On 25 March 2026, researchers reported that a GlassWorm variant used Solana transaction memos as another form of blockchain dead drops. The developer-targeting supply chain malware queried Solana through JSON-RPC, obtained a designated transaction and parsed its memo for an IP address or domain pointing to live C2 infrastructure.

The variant could fall back to other dead-drop channels if the memo did not provide a usable result. Reported network indicators included 45.32.150[.]251, 217.69.3[.]152 using the path /wall, and 45.150.34[.]158.

Timeline and current exploitation status

The activity described by Talos reflects several years of real-world development rather than a newly proposed technique:

  • 4 September 2019: Glupteba’s Bitcoin-backed C2 update mechanism was publicly documented.
  • 7 December 2021: Google disrupted Glupteba and confirmed its Bitcoin fallback channel.
  • 13 to 17 October 2023: EtherHiding activity on BNB Smart Chain was documented.
  • 30 January 2026: ClearFake telemetry involving BNB Smart Chain endpoints was published.
  • 25 March 2026: Solana memo C2 retrieval by GlassWorm was reported.
  • 29 June 2026: TONResolver’s smart contract based domain rotation was detailed.
  • 18 November 2026: Talos published its cross-chain analysis and defensive guidance.

These cases affect malware delivery ecosystems rather than vulnerable blockchain product versions. Relevant environments include Windows systems infected by Glupteba or TONResolver, websites compromised to deliver ClearFake, browsers exposed to its false-update chain, and developer environments targeted by GlassWorm.

Defending against blockchain dead drops

Organisations should first establish whether outbound access to public blockchain RPC services is required. Where it is not, egress controls can restrict JSON-RPC traffic and access to gateways such as tonapi[.]io or unexpected BNB Smart Chain and Solana endpoints.

Where blockchain access is legitimate, monitoring should connect network events with process behaviour. High-value detections include MSHTA, PowerShell, browsers or unexpected Node.js processes contacting RPC services, followed by connections to newly observed domains or IP addresses.

Endpoint telemetry and memory analysis are also important because configurations may never touch disk. Investigators should look for encoded contract responses, in-memory decryption, unusual Node.js persistence and repeated blockchain queries immediately before C2 beaconing. These controls address the retrieval behaviour behind blockchain dead drops, rather than depending solely on blocking the attacker’s latest domain.

Originally reported by blog.talosintelligence.com.

Share this bulletin

About the Author

Rob McBride Headshot - CyPro Partner and leading cyber security expert

Rob McBride

Partner

  • CISSP
  • ACA Chartered Accountant
  • MPhil
  • BSc
  • SOC 2
  • ISO 27001

Rob McBride

Rob is a Founding Partner at CyPro and a highly experienced CISO. Beginning his career with a successful tenure at Deloitte, Rob has since amassed a wealth of experience, notably serving as a cyber security advisor to the UK government and spearheading cloud security transformations for several global banks.

At CyPro, Rob leads the managed service business line, working extensively across multiple sectors including telecommunications, technology, higher education, travel, and retail. He is passionate about equipping small and medium-sized businesses (SMBs) with robust cyber security strategies to fuel their growth.

View Profile
Back to Bulletins

Related CyPro Services

  • Managed Detection and Response (MDR)

    Managed Detection and Response (MDR) is an end-to-end managed service designed to help organisations detect, analyse and respond to cyber threats quickly and effectively. It...
    View Service
CyPro Cookie Consent

Hmmm cookies...

Our delicious cookies make your experience smooth and secure.

Privacy PolicyOkay, got it!

We use cookies to enhance your experience, analyse site traffic, and for marketing purposes. For more information on how we handle your personal data, please see our Privacy Policy.

Schedule a Call