Researchers from Checkmarx recently uncovered a sophisticated supply chain attack within the Node Package Manager (NPM) ecosystem, blending traditional malware tactics with blockchain-based command-and-control (C2) operations. This attack, marked by its use of the Ethereum blockchain, reveals an evolving threat in the software development sector, targeting developers through a malicious package disguised as a legitimate JavaScript testing tool.
This malicious package, named “jest-fet-mock,” was engineered to deceive developers by imitating a well-known testing utility. Designed with a multi-platform malware structure, the attack exploits Ethereum smart contracts as a unique C2 mechanism. Checkmarx researchers noted that while blockchain technology is generally used to support decentralized applications and digital assets, its integration into malware strategies represents a significant innovation in cyber threat tactics.
Attack Mechanics and Deceptive Distribution Techniques
The package, “jest-fet-mock,” surfaced in mid-October and masquerades as a JavaScript utility, using the typosquatting technique to target developers. By subtly misspelling the package name “fetch-mock-jest” as “fet,” the attackers crafted a near-perfect imitation of popular packages such as “fetch-mock-jest” and “Jest-Fetch-Mock.” The former attracts roughly 200,000 downloads per week, while the latter reaches over a million weekly downloads, making them prime targets for impersonation. This small typo could easily trick developers into downloading the malicious package, unaware of its hidden agenda.
Once installed, the malicious package leverages NPM preinstall scripts to execute harmful code on targeted systems, including Windows, Linux, and macOS platforms. It then initiates info-stealing functions, which allow the malware to access sensitive information within the development environment. This malware secures persistence through customized system mechanisms, remaining active even after initial installation. All variations of the package communicate with a remote C2 server, where attackers can monitor infected systems and escalate the attack.
Ethereum’s Role in Command-and-Control Operations
In an unusual twist, the attackers utilize the Ethereum blockchain to establish C2 communication, marking one of the first times this method has appeared in the NPM ecosystem. An Ethereum smart contract associated with the attack, located at the address “0xa1b40044EBc2794f207D45143Bd82a1B86156c6b,” uses its “getString” function to distribute C2 server addresses to infected systems. This blockchain-based approach leverages the security and decentralized nature of blockchain, which makes it difficult for traditional cybersecurity tools to detect or remove. This innovation allows attackers to maintain a resilient C2 infrastructure, immune to takedowns and monitoring due to blockchain’s immutability.
Threat Analysis and Response Challenges
Further analysis from Checkmarx revealed that the malware variants were crafted for specific operating systems, each with unique SHA-256 identifiers:
Windows: df67a118cacf68ffe5610e8acddbe38db9fb702b473c941f4ea0320943ef32ba
Linux: 0801b24d2708b3f6195c8156d3661c027d678f5be064906db4fefe74e1a74b17
macOS: 3f4445eaf22cf236b5aeff5a5c24bf6dbc4c25dc926239b8732b351b09698653
These malware samples have yet to be flagged as malicious by the security detection tools available on VirusTotal, allowing the attack to evade conventional detection methods. This undetected presence poses an ongoing risk to development environments, as NPM utilities are often integrated into critical Continuous Integration and Continuous Deployment (CI/CD) pipelines. This attack could enable threat actors to infiltrate CI/CD processes, potentially compromising entire software supply chains.
In addition to Checkmarx’s findings, Phylum and Socket have reported further malicious packages linked to this campaign, indicating a larger, escalating threat within the NPM ecosystem. The attackers’ use of blockchain as a C2 mechanism reflects an evolution in supply chain attack strategies that outpaces many traditional cybersecurity approaches, which may struggle to monitor or intercept blockchain-based communications effectively.
Mitigation and Vigilance for Development Teams
This attack underscores the importance of enhanced security practices for software development teams. Given the campaign’s sophisticated deception techniques and its use of blockchain infrastructure, developers are urged to rigorously review their package management practices. Experts recommend verifying the authenticity of testing utilities and implementing strict security protocols to prevent similar intrusions.
In response to this incident, Checkmarx emphasizes the need for more robust security measures across development environments to combat such advanced supply chain attacks. By understanding the vulnerabilities exposed by “jest-fet-mock” and similar packages, organizations can better protect their CI/CD workflows and overall software supply chain integrity. This attack represents a significant warning to the industry, urging vigilance as attackers leverage emerging technologies like blockchain to create more resilient and elusive cyber threats.
