CRITICAL npm Malware

Malicious code in resolve-audit (npm)

MAL-2026-13987 · GHSA-69qf-g8jq-47xv

Published · Modified

Dependency scanning

Check whether resolve-audit 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 (86b902b4dc4c2187bb95548ed903dfea70ea626ba5450f031c2cb27b3639dd1c)

resolve-audit@99.9.1 is a stub package (index exports an empty object) whose package.json declares its only dependency ltidisafe as a direct HTTPS tarball URL: https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.6.tgz. On npm install, npm fetches this arbitrary tarball from an anonymous, mutable Google Cloud Storage bucket (path segment depenconf, a dependency-confusion marker) rather than resolving through the npm registry, with no version-by-hash pinning. Any lifecycle scripts inside that tarball execute on the installer. The version number 99.9.1 is characteristic of dependency-confusion/version-squat lures designed to win resolution against a private-registry package of the same name.

Source: ghsa-malware (58ff2b4a4d1fb90a19c0d2673633f06ecc737fd284d08676fadb90bef8b3cf9c)

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.

Ready to move

Start Securing

Free, no credit card | First findings in minutes