Threat Intelligence

ChainScript RAT Shows Why Relying on Indicator-Based Detection Is No Longer Viable

New ChainScript RAT uses Polygon smart contracts to rotate C2, exposing the limits of traditional indicator-based defenses.

Published: Sep 21, 2026 • 5 min read • By FirstNews editorial desk
Source image via thehackernews.com
Key Vulnerability Findings
  • • ChainScript RAT uses a Polygon smart contract to discover and rotate its WebSocket C2.
  • • The malware is delivered via ClickFix lures masquerading as popular SaaS tools.
  • • Traditional IOC-based defenses struggle to keep pace with decentralized, blockchain-enabled infrastructure.

New ChainScript RAT Undermines Indicator-Based Defenses

The Blackpoint Adversary Pursuit Group disclosed that a previously undocumented remote-access trojan, ChainScript, is being distributed through ClickFix-style lures and uses a Polygon smart contract to rotate its command-and-control (C2) infrastructure. The findings, published on September 21, 2026, demonstrate a concrete failure of traditional indicator-of-compromise (IOC) models that rely on static domain, IP, or hash signatures Thehackernews.

Attack Vector: ClickFix Lures Masquerading as Trusted SaaS

ChainScript first appears as a Windows installer (e.g., ComponentTask33-4d14e6ac.msi) that pretends to be Spotify, Zoom Workplace, or Microsoft Teams. The installer is launched via msiexec.exe after a user clicks a malicious ad on a compromised Reddit account or a fake search result. Inside the MSI, a hidden PowerShell script drops the Node.js runtime, the JavaScript-based agent, and auxiliary binaries into %LOCALAPPDATA% under Microsoft-looking folder names. A VBScript file then serves as the primary launcher, invoking the agent with elevated privileges.

Persistence and Execution Flow

The agent establishes user-level persistence through a scheduled task, with a Registry Run key as a fallback. Once the system boots, the scheduled task triggers the VBScript, which in turn starts the JavaScript agent. The agent opens a WebSocket connection to a resolver address obtained from a Polygon smart contract. This contract stores the current C2 endpoint, enabling the attacker to change the backend without recompiling the implant. The design mirrors the “EtherHiding” technique observed in other recent malware families.

Capabilities of the ChainScript RAT

ChainScript offers a full suite of remote-administration functions:

  • Interactive cmd.exe and PowerShell shells.
  • File upload/download, directory listing, and deletion.
  • Screenshot capture and webcam snapshot.
  • Execution of arbitrary JavaScript on the victim.
  • Enumeration of cryptocurrency wallets in desktop applications and browser extensions.
  • Self-update and persistence removal commands. These capabilities place the malware squarely in the high-risk category for enterprise environments that host valuable crypto assets or intellectual property.

Why Blockchain-Based C2 Is a Game-Changer

The use of a Polygon contract as an external resolver separates the discovery mechanism from the implant. When a sinkhole or takedown request targets the current WebSocket server, the attacker simply updates the contract to point to a new endpoint. Because the contract address remains constant, static IOCs such as domain hashes or IP ranges become obsolete after the first rotation. This architecture challenges the long-standing assumption that signature-based detection can reliably block malware.

Broader Campaign Context: PasteSwitch and MacStealers

The ChainScript deployment is part of a larger PasteSwitch operation that compromised HBO Max’s verified Reddit account to push malicious ads. The same campaign delivers macOS stealers (MacSync, Atomic macOS Stealer) and Windows stealers (Amatera, AnimateClipper, ZigClipper). Over a 48-hour window in mid-September 2026, the Reddit account served 108 malicious ads, targeting regions with high macOS enterprise adoption and active Web3 communities. The macOS side also uses a server-side browser-fingerprinting gate to hide the lure from crawlers, further reducing the effectiveness of automated sandboxing.

Indicator Fatigue

Security teams that rely on hash-based blocklists or domain reputation feeds will see rapid decay in coverage. The Polygon contract can be updated multiple times per day, rendering any captured C2 address stale within hours.

Threat-Hunting Adjustments

Analysts must shift toward behavioral detection: monitoring for anomalous Node.js runtimes, unexpected PowerShell scripts that drop binaries into %LOCALAPPDATA%, and scheduled tasks that launch VBScript files. Correlating these events with blockchain queries (e.g., monitoring Polygon contract interactions from corporate networks) can provide an early warning signal.

Network Controls

Outbound traffic to known Polygon RPC endpoints (e.g., https://polygon-rpc.com) should be inspected or restricted. Deploying DNS-level blocklists for known smart-contract interaction domains can reduce exposure, though attackers may pivot to alternative RPC providers.

Mitigation Guidance

  1. Patch the installer chain – Ensure that Windows Defender Application Control (WDAC) or similar application whitelisting solutions block unsigned MSI packages from untrusted sources.
  2. Hard-enforce PowerShell execution policies – Set ExecutionPolicy to AllSigned and enable script block logging to capture hidden PowerShell stages.
  3. Monitor scheduled tasks – Alert on new tasks that reference scripts located in %LOCALAPPDATA% and that execute cscript.exe or wscript.exe.
  4. Restrict Node.js runtimes – Use endpoint protection to flag the installation of Node.js in user profiles where it is not required.
  5. Inspect blockchain traffic – Deploy a network sensor that logs HTTP POST requests to known Polygon RPC URLs; flag any internal host that queries a contract address matching the one observed in the ChainScript sample.

The Controversial Take: Indicator-Based Defenses Are Obsolete

The prevailing industry narrative still promotes signature-centric security as a baseline. ChainScript’s architecture proves that this model is fundamentally broken against adversaries who can externalize C2 discovery to immutable blockchain contracts. While signatures remain useful for known malware families, the rapid rotation enabled by smart contracts means that static IOCs provide a false sense of security. Security programs must invest in contextual, behavior-driven telemetry and blockchain-aware network monitoring to stay ahead.

What to Watch Next

  • Further Polygon contracts – Researchers should monitor public Polygon contract registries for patterns that match the ChainScript resolver structure.
  • Cross-platform payloads – The same delivery chain may be adapted for Linux or Android, leveraging the same blockchain C2 technique.
  • Regulatory response – As blockchain-enabled malware gains traction, agencies such as CISA may issue advisories on monitoring smart-contract interactions.

For a deeper look at how threat actors are abusing private repositories to hide backdoors, see the analysis of Transparent Tribe’s Rust backdoor campaign.


This article adheres to Fastest News AI’s editorial standards, providing actionable intelligence for security engineers and incident responders.

Related coverage

Explore more on this topic

Frequently Asked Questions

What is ChainScript RAT?

ChainScript is a newly discovered remote-access trojan that provides CMD, PowerShell, file, screenshot, and crypto-wallet enumeration capabilities.

How does the Polygon contract help the malware?

The contract acts as an external resolver; the implant queries it to obtain the current WebSocket endpoint, allowing the attacker to shift C2 without changing the binary.

Sources

Related Security Coverage