Malicious code in in-install (npm)
The npm package in-install@99.9.1 contains malicious code that fetches and executes an arbitrary tarball from a mutable Google Cloud Storage bucket during installation. The package declares a dependency on ltidisafe as an HTTPS tarball URL rather than a registry-resolved package, allowing the bucket owner to modify the delivered code at any time without version changes.
- Disclosed
- Last updated
- Blast radius
- Any developer or CI/CD system that installed in-install@99.9.1
- Ecosystems
- Attack vectors
- Affected entities
- in-install · 99.9.1
The npm package in-install@99.9.1 was found to contain malicious code that executes arbitrary code at install time. The package declares its ltidisafe dependency as an HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.9.tgz) hosted on a Google Cloud Storage bucket, rather than as a registry-resolved package.\n\nWhen npm install in-install is executed, the tarball is fetched and installed into the installer's node_modules directory, executing any install-time or import-time code it contains. The bucket path is mutable and not subject to npm registry review, meaning the bytes delivered can be changed at any moment without a version bump or audit trail.\n\nThe package's own index.js is an empty export, indicating the sole observable effect of installation is pulling arbitrary off-registry code into the installer's environment. This represents a supply chain attack vector where the malicious package acts as a vector to inject unreviewed, mutable code into developer and CI/CD environments.\n\nThe incident was identified and credited to the OpenSSF's malicious-packages project.
Indicators of compromise
- Packages
- in-install@99.9.1
- Domains
- ltidi.storage.googleapis.com
Remediation
- Immediately uninstall in-install@99.9.1 from all environments
- Audit npm audit logs and package-lock.json files to identify systems that installed this package
- Review any systems that installed this package for signs of compromise or unauthorized code execution
- Clear npm cache and reinstall dependencies from a clean state
- Consider rotating credentials and secrets on any systems that may have been affected
- Monitor for any suspicious activity or data exfiltration from affected systems
Sources
- GitHub Advisory GHSA-5q6v-3rg4-8rf8 · GitHub Advisory Database
Cite this entry
"Malicious code in in-install (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 13, 2026; last updated August 13, 2026. https://supplychainattack.org/incident/malicious-code-in-in-install-npm-l1ajer
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package