Skip to main content
Mallory
← Back to News
package-repository-poisoningcredential-stealer-activityvendor-distribution-compromisebuild-pipeline-compromise

Compromised jscrambler npm Release Executed Cross-Platform Rust Infostealer

Supply Chain Risk · 15 sources · Updated 4mo ago · First seen Jul 11, 2026

Compromised jscrambler npm Release Executed Cross-Platform Rust Infostealer

The npm package jscrambler was compromised through malicious version 8.14.0, which added an undocumented preinstall hook and install-time files that executed hidden native binaries on Windows, macOS, and Linux during npm install, before application code ran. Researchers said the release appeared to be published directly to npm from a legitimate maintainer account without matching source repository commits or tags, pointing to a likely compromise of the maintainer account or build pipeline. Socket reported detecting the release within minutes of publication and alerted the maintainers, while a subsequent 8.15.0 release appeared clean.

Further analysis linked the package to a Rust-based infostealer aimed at developer workstations and CI/build environments, creating exposure for source code, environment variables, build credentials, deployment tokens, and other secrets. Reported targets included cloud credentials, browser data, messaging sessions, cryptocurrency wallets, Bitwarden vault contents, and configuration files for AI coding tools such as Claude Desktop, Cursor, Windsurf, VS Code, and Zed. Researchers also observed anti-debugging on Windows and macOS, Linux eBPF capability, persistence through Windows scheduled tasks and macOS LaunchAgents, and encrypted command-and-control details; because 8.14.0 remained available on npm, pinned installs on older npm clients that still run install scripts could continue to trigger the payload.

Does this reach your builds?Trace attribution and downstream blast radius.
Trace the chain
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

9 events · Jun 10, 2026 – Jul 14, 2026
  1. Jul 14, 20264mo ago

    Jscrambler says dependent npm packages were also affected

    Jscrambler disclosed that the supply-chain compromise extended beyond the main jscrambler package to dependent packages including jscrambler-webpack-plugin, gulp-jscrambler, grunt-jscrambler, and jscrambler-metro-plugin. This expanded the scope of the incident to multiple related npm packages.

    Multiple Jscrambler Packages Impacted by Supply Chain Attack - SecurityWeek
  2. Jul 13, 20264mo ago

    Jscrambler revokes npm credential and releases clean version 8.22.0

    Jscrambler said an attacker used an npm publishing credential to upload the unauthorized releases. The company responded by revoking credentials, deprecating the affected versions, and publishing a clean 8.22.0 release.

    Hackers Compromised jscrambler With 15,800+ Weekly Downloads to Attack Developers
  3. Jul 13, 20264mo ago

    Jscrambler discloses 1,479 downloads during two-hour compromise window

    Jscrambler said the unauthorized malicious jscrambler npm releases were available for roughly two hours and were downloaded about 1,479 times. The company advised affected users to treat their environments as compromised, rotate secrets, restore from safe backups, and update to safe versions.

    Hackers backdoor Jscrambler npm package with infostealer malware
  4. Jul 13, 20264mo ago

    JFrog links jscrambler malware to IronWorm and self-propagation code

    JFrog assessed the malware in the compromised jscrambler releases as an evolved IronWorm variant. Its analysis also found code that attempted to steal npm tokens and republish trojanized packages to the npm registry, indicating possible self-propagation across the ecosystem.

    Compromised Jscrambler npm Releases Target Developer Environments with Cross-Platform Rust Infostealer - CySecurity News - Latest Information Security and Hacking Incidents
  5. Jul 11, 20264mo ago

    Additional malicious jscrambler versions published after 8.15.0

    Reporting identified further compromised jscrambler npm releases—8.16.0, 8.17.0, 8.18.0, and 8.20.0—after the initial 8.14.0 incident. These later versions reportedly shifted the malware from an install-time hook into the CLI execution path, continuing delivery of a cross-platform Rust-based infostealer.

    jscrambler npm Releases Dropped a Rust Infostealer
  6. Jul 11, 20264mo ago

    jscrambler 8.15.0 replaces the malicious npm release

    Version 8.15.0 was released as a replacement for the compromised 8.14.0 package and was reported to appear clean. However, the malicious 8.14.0 version remained available on npm, leaving pinned installs and older npm clients at risk if they still executed install scripts.

    Compromised jscrambler 8.14.0 npm Release Drops Rust Infostealer During Install
  7. Jul 11, 20264mo ago

    Socket detects compromised jscrambler release and alerts maintainers

    Socket detected the malicious jscrambler 8.14.0 release six minutes after it was published and reported the issue to the package maintainers. The detection identified the new install-time behavior as a supply-chain compromise affecting developer workstations and CI/build environments.

    jscrambler npm Package Compromised in Supply Chain Attack - ...
  8. Jul 11, 20264mo ago

    Malicious jscrambler 8.14.0 release published to npm

    A compromised version of the npm package jscrambler, 8.14.0, was published to npm with an undocumented preinstall hook and install-time files that executed hidden native binaries on Windows, macOS, and Linux. Reporting indicates the release was likely pushed from a legitimate maintainer account without matching source repository commits or tags.

    jscrambler npm Package Compromised in Supply Chain Attack - ...
  9. Jun 10, 20265mo ago

    Compromised Rust crate onering disclosed with code exfiltration behavior

    Aikido reported that the Rust crate onering was compromised and performed code exfiltration. This introduces a separate affected package outside the previously documented jscrambler npm incident.

    Aikido Dev Blog
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Malware

1 linked

Organizations

1 linked
Jscrambler

Breaches

1 linked
JSCRAMBLER-2026-07

Observables

11 linked

Indicator values are masked on this page. View all 11 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
Trace the Supply Chain
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.