Hackers Compromised jscrambler With 15,800+ Weekly Downloads to Attack Developers
\n \t
\n
<\/BR>
\n
\n \t
\n
<\/BR><\/p>\n
A supply chain attack on the Socket Research Team detected the first malicious release, jscrambler@8.14.0, on July 11, 2026, only six minutes after publication.<\/p>\n The compromised release added an undocumented preinstall script, causing malicious code to execute automatically when a developer ran npm install. Victims did not need to import the package or run its command-line tool for the payload to launch.<\/p>\n The attack affected versions 8.14.0, 8.16.0, 8.17.0, 8.18.0, and 8.20.0. Jscrambler later confirmed that an attacker used an npm publishing credential<\/a> to upload the unauthorized releases.<\/p>\n The company revoked and rotated publishing credentials, deprecated the affected versions, and released clean version 8.22.0.<\/p>\n In the early malicious releases, the attackers inserted a preinstall hook that launched dist\/setup.js. This loader read a disguised binary container named dist\/intro.js, selected a payload based on the victim\u2019s operating system, and wrote it to a hidden temporary file.<\/p>\n It then started the executable in the background without displaying output or requiring user interaction. The container held three Rust-based binaries: a Linux ELF file, a Windows PE executable, and a macOS Apple Silicon Mach-O binary.<\/p>\n Starting with version 8.18.0, the attackers removed the install hook and injected the same loader into the package\u2019s main JavaScript files.<\/p>\n This allowed the malware to run when an application imported jscrambler or when its CLI was executed, bypassing checks focused only on npm lifecycle scripts.<\/p>\n According to the Socket Research Team<\/a>, the malware was designed to steal high-value developer and cloud credentials, targeting browser data, cryptocurrency wallets, Discord, Slack, Telegram, Steam sessions, cloud tokens, and local OS keyrings.<\/p>\n It also searched for configuration files used by AI coding tools, including Claude Desktop, Cursor, Windsurf, VS Code, Zed, and MCP server configurations, which can contain API keys and sensitive connection details.<\/p>\n The payload also attempted to access credentials for AWS<\/a>, Google Cloud, and Microsoft Azure. It included references to cloud metadata endpoints, secret-management services, Kubernetes APIs, and deployment environments.<\/p>\n This poses a serious risk to software developers because build systems and CI pipelines often contain source code, signing keys, deployment tokens, and production credentials.<\/p>\n To slow analysis, the malware encrypted around configuration strings using ChaCha20-Poly1305 encryption. Researchers also identified network code that appeared to upload stolen data via encrypted TLS connections<\/a>, using a multipart HTTP request to the\/upload endpoint.<\/p>\n Organizations should immediately remove affected Users should upgrade to verified clean version 8.22.0 and review lockfiles for transitive references to compromised versions.<\/p>\n The incident highlights how a stolen npm publishing credential can turn a trusted developer dependency into an effective entry point for credential theft and cloud compromise.<\/p>\n Indicators of Compromise<\/strong><\/p>\n Note:\u00a0<\/strong>IP addresses and domains are intentionally defanged (e.g., [.]) to prevent accidental resolution or hyperlinking. Re-fang only within controlled threat intelligence platforms such as MISP, VirusTotal, or your SIEM.<\/em><\/p>\n \u00a0Strengthen Your SOC by Accelerating Threat Detection & Rapid Investigations.\u00a0-> Integrate ANY.RUN With Your SOC <\/a>Now<\/a><\/strong>.<\/strong><\/p>\n The post Hackers Compromised jscrambler With 15,800+ Weekly Downloads to Attack Developers<\/a> appeared first on Cyber Security News<\/a>.<\/p>\n<\/div>\njscrambler<\/code> npm package, a JavaScript code-protection tool with over 15,800 weekly downloads, involved malicious versions that silently deployed native malware<\/a> on Linux, macOS, and Windows systems.<\/p>\nHackers Compromise jscrambler Package<\/strong><\/h2>\n
jscrambler<\/code> versions, audit npm installation and CI logs, and rotate credentials exposed on impacted developer systems and build servers.<\/p>\n\n\n
\n IOC Type<\/strong><\/th>\n Indicator<\/strong><\/th>\n<\/tr>\n<\/thead>\n\n \n Affected Versions<\/strong><\/td>\n \n jscrambler<\/code> 8.14.0, 8.16.0, 8.17.0, 8.18.0, 8.20.0<\/td>\n<\/tr>\n\n Patched Version<\/strong><\/td>\n \n jscrambler<\/code> 8.22.0<\/td>\n<\/tr>\n\n Preinstall Hook<\/strong><\/td>\n preinstall: node dist\/setup.js<\/code><\/td>\n<\/tr>\n\n Dropped Files<\/strong><\/td>\n \n dist\/setup.js<\/code>, dist\/intro.js<\/code>\n<\/td>\n<\/tr>\n\n Loader SHA-256<\/strong><\/td>\n a742de963f14a92d24ebcbc7b44ac867e23a20d31d1b0094a13a4f83287f4e60<\/code><\/td>\n<\/tr>\n\n Payload SHA-256<\/strong><\/td>\n a41a523ef9517aab37ed6eea0ec881821bdcb7aefcb5c5f603adc7907f868c86<\/code><\/td>\n<\/tr>\n\n package.json SHA-256<\/strong><\/td>\n bba32ddeab075a5e5015eec50f5d2af364c95b848732c714aea6b6baf78f49f0<\/code><\/td>\n<\/tr>\n\n Linux ELF SHA-256<\/strong><\/td>\n fbbcf4d8f98168f78f5c0c47a9ae56d59ec8ac84a7c9ca6b797fedfb8d62d2bd<\/code><\/td>\n<\/tr>\n\n Windows PE SHA-256<\/strong><\/td>\n b7ca95d1b23c8e67416a25cedf741de0917c2096bbc9d24649eea7853d054903<\/code><\/td>\n<\/tr>\n\n macOS Mach-O SHA-256<\/strong><\/td>\n c8fd47d36bdf7c825378593ab82ed8c24d1dc52e26b507812393e24e1d5201fd<\/code><\/td>\n<\/tr>\n\n File Signature<\/strong><\/td>\n \n 1b 43 53 49 01<\/code> (x1bCSIx01<\/code>)<\/td>\n<\/tr>\n\n Execution Artifact<\/strong><\/td>\n Hidden temp executable<\/td>\n<\/tr>\n \n Process Artifact<\/strong><\/td>\n Detached spawn()<\/code> process<\/td>\n<\/tr>\n\n Network IOC<\/strong><\/td>\n \n POST \/upload<\/code> (multipart\/form-data)<\/td>\n<\/tr>\n\n Cloud Metadata<\/strong><\/td>\n \n 169.254.169[.]254<\/code>, 169.254.170[.]<\/code>2<\/code>, metadata.google.internal<\/code>\n<\/td>\n<\/tr>\n\n Recon Endpoints<\/strong><\/td>\n \n check.torproject.org\/api\/ip<\/code>, 1.1.1.1<\/code>, 8.8.8.8<\/code>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n