A compromised publishing credential let attackers push five malicious versions of the jscrambler npm package, including 8.14.0, 8.16.0, 8.17.0, 8.18.0, and 8.20.0, on July 11, each carrying a cross-platform Rust-based infostealer built to harvest AWS, Azure, and Google Cloud keys, cryptocurrency wallets, password manager data, browser sessions, and AI tool API keys, according to jscrambler’s own security advisory. The malicious release also shipped kernel-level persistence on Linux and anti-debugging protections on Windows and macOS, the kind of engineering effort that signals a deliberate, well-resourced operation rather than an opportunistic dump. Security firm Socket detected the malicious release six minutes after it was published, and jscrambler confirmed a compromised publishing credential as the attack vector. Version 8.22.0 is confirmed clean.
The package’s weekly download count, around 15,800, is modest next to the ecosystem-wide npm compromises CyberTech has tracked, but that is exactly why it matters. jscrambler is a code-obfuscation and application-security tool, meaning developers pull it into their build pipeline specifically to protect production code, then trust it with privileged access to the same environment it is meant to secure. A six-minute detection window is unusually fast for the npm ecosystem, yet the payload’s design, targeting cloud credentials and AI tool keys specifically, shows attackers are increasingly building infostealers around what a modern developer’s machine actually holds rather than generic browser data.
The original insight for security leaders is that publishing-credential compromise, not a vulnerable dependency, is now the recurring root cause across this year’s npm supply chain incidents, which means dependency scanning alone will not catch it. CyberTech previously covered how a similar credential-based compromise hit Red Hat’s own npm packages, exposing developer cloud and Vault credentials. Teams that rely on security tooling packages specifically, given their elevated build-pipeline trust, should pin exact versions rather than accepting automatic minor or patch updates, and should treat any tool with direct access to secrets as requiring the same publish-integrity monitoring applied to production infrastructure itself.
Source: jscrambler
