Malicious code in napi-raw (npm)
MAL-2026-13984 · GHSA-588j-2jx3-7mqj
Published · Modified
Dependency scanning
Check whether napi-raw 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 (d002132bfd19338c8fbc1cc3775c1c8b7be3d059c642881c4dd92be67bf7c895)
napi-raw@99.9.1 is a near-empty wrapper (main exports {}, no lifecycle scripts) whose only effect on install is to declare ltidisafe as a dependency pointed at an arbitrary HTTPS tarball on a generic Google Cloud Storage bucket: "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.1.tgz". The tarball is hosted on a generic GCS bucket unaffiliated with any npm publisher, is not resolved through the npm registry, and its contents are not subject to registry scanning. Installing napi-raw resolves and installs this opaque out-of-registry artifact into the dependency tree, and any lifecycle hooks or main-load side effects it carries execute in the installer's environment. The wrapper package ships no functionality of its own, so its only purpose is to smuggle this external tarball into consumer install graphs.
Source: ghsa-malware (2d3025669f65165c9680a8514ca6a0cfc8bcac60e7d53d4c3a58b43866d09b28)
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.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes