Nearly 800 npm Packages Deliver Cross‑Platform RAT and Infostealer

On August 2026, The Hacker News reported that nearly 800 malicious npm packages had been published to the npm registry as part of a new campaign designed to deliver cross‑platform malware targeting Windows, Mac, and Linux systems. ¹

The attackers used AI slop squatted—randomly generated typo‑squatting package names—to evade detection by name alone. Prior typosquat campaigns relied on manually identifying common misspellings.

All of these packages deliver a powerful Remote Access Trojan (RAT) alongside an infostealer payload. The RAT gives attackers full control over infected machines while the infostealer harvests credentials, browser cookies, system information, and other sensitive data. ¹

Technical analysis suggests the malicious code likely compile native modules using tools such as `gcc` or Clang, enabling it to bypass many JavaScript security sandboxes that would flag interpreted scripts as malicious. By embedding compiled binaries inside Node.js projects, the attacker gains execution privileges even when the host environment attempts to sandbox untrusted scripts.

A similar incident involving XZ Utils in March 2024 demonstrated how even core system utilities could be compromised through seemingly innocuous contributions, underscoring the continued risk posed by supply‑chain attacks targeting open‑source repositories.

Developers who rely on npm for dependencies are at risk if they install these packages unknowingly. The attack vector highlights the importance of rigorous dependency hygiene: verifying publisher reputation, reviewing source code where possible, and monitoring updates for suspicious changes. ¹

Mitigation advice from experts includes using lockfiles and integrity checks to ensure installed code matches what was originally published; employing tools like `npm audit`, Snyk, or GitHub’s Dependabot can surface anomalous packages before they reach production systems. Additionally, developers should consider scanning package names against known typo‑squatting patterns and restricting automatic installation of new dependencies in critical environments.

The scale of this campaign—nearly 800 distinct malicious packages—indicates that attackers aim for broad distribution rather than targeted compromise. As the npm ecosystem continues to grow, vigilance around package provenance remains essential to protect both individual users and enterprise deployments from cross‑platform remote access trojans and infostealers.