Fake Web3 Accelerator Distributes Malware Through Malicious npm Packages

A recent report by The Hacker News uncovered a scheme in which a counterfeit “Web3 accelerator” pushed malicious npm packages to Windows and macOS systems under the pretext of offering free artificial intelligence (AI) credits for Anthropic Claude and Google Gemini, coding tools, and security audits. The attackers bundled information‑stealers and backdoors into these packages, targeting developers who rely on npm libraries for their projects. Elastic, an analyst quoted in the story, described how the delivered tools exfiltrated data and installed persistent backdoors on affected machines. ¹

The operation exploited the trust that developers place in npm’s vast ecosystem. By publishing seemingly legitimate dependencies, the actors ensured that the code would be executed automatically when a project imported or ran those modules. Once inside the target environment, the payload accessed system credentials, keystrokes, and other sensitive data before silently transmitting it to remote command-and-control servers. Because the attack masqueraded as an incentive program, many users fell prey without suspecting foul play. The same technique had been used previously with typosquatting—for example, “request-js” instead of “requests”—but this incident marks the first known use within a mainstream package registry like npm where vetting processes are imperfect. ¹

Experts note that malware distribution via npm is not new; researchers identified malicious code hidden in popular libraries such as ‘jquery-ui’ in 2018, affecting thousands of installations worldwide. This latest campaign combines two high‑impact tactics: distributing malware through trusted development tools and hijacking AI agent traffic. In earlier cases, attackers redirected user sessions via compromised VPN servers; here they leveraged the same principle but embedded the compromise directly into the build pipeline. Experts warn that more attacks exploiting open source vulnerabilities are likely as adversaries refine their ability to blend malicious code into widely used ecosystems. ¹

The fallout from this breach extends beyond individual developers. Organizations that rely on third‑party AI services—such as Anthropic Claude or Google Gemini—to power internal tooling now face potential exposure of proprietary data if those services are accessed through infected local environments. Moreover, any downstream consumers of the npm packages may unknowingly propagate the backdoors across corporate networks, amplifying the attack’s reach. The Hacker News report underscores the need for rigorous dependency scanning and continuous monitoring of npm registries for anomalous activity. Developers should verify package integrity using checksums, lock files, and signed releases whenever possible. ¹

While no specific numbers were disclosed regarding how many systems were affected, the scale could be substantial given the ubiquity of npm in modern software stacks. Elastic cautioned that the attackers’ use of “free AI credits” was a social‑engineering ploy designed to lower vigilance among users eager to experiment with cutting-edge models. As the incident demonstrates, even seemingly benign incentives can mask sophisticated threats aimed at extracting sensitive information from development machines. ¹

In response, several security vendors have issued advisories urging immediate audit of npm dependencies and removal of suspicious packages from active projects. Open source communities are also reviewing their vetting processes to prevent similar incidents. Until such measures become standard practice, developers must remain vigilant about where they obtain code and how it is integrated into production workflows. Failure to do so risks exposing personal or organizational data to malicious actors who exploit trust within widely used ecosystems.