Malicious code in gunzip-js (npm)
MAL-2026-14056 · GHSA-2hqf-5jxh-4wp2
Published · Modified
Dependency scanning
Check whether gunzip-js is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (d410844f9db44f33c2f674456c727d4c46402ad8f4de02a036fec3b099b2737b)
gunzip-js@99.9.1 is a near-empty npm package (typosquat of the well-known gunzip-maybe / gunzip family) whose package.json declares its sole dependency ltidisafe as an HTTPS tarball URL — https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.7.2.tgz — instead of a version resolved from the npm registry. On npm install, npm downloads that tarball from the anonymous Google Cloud Storage bucket and installs it into node_modules, executing any lifecycle scripts (preinstall/install/postinstall) and any top-level code reached via require. The GCS bucket is not associated with any known publisher, the path segment depenconf mirrors the term dependency-confusion, the version 99.9.1 is the classic high-number squat pattern, and the package's own index.js is empty — the only effect of installing gunzip-js is to pull attacker-controlled code from an unaudited external host into the installer's dependency graph.
Source: ghsa-malware (9c6e55e77d4b3cbb1fefb101880e5e01540189c921ca9ef6432781d2807e71ea)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Source: ossf-package-analysis (cb01fea066eb17256cd8a5ef589351ca7c5fda77eaff201237eac8f306b5b53d)
The OpenSSF Package Analysis project identified 'gunzip-js' @ 99.9.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes