Which versions of resolve-audit are malicious?

The following npm versions of resolve-audit are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate resolve-audit if I installed it?

Remove resolve-audit from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed resolve-audit — how do I know if it already compromised me?

If resolve-audit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is resolve-audit part of a known attack campaign?

Yes — resolve-audit is associated with the IN-MAL-2026-017677 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find resolve-audit across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for resolve-audit (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging resolve-audit across your stack and pipelines.

Malicious package

resolve-auditnpm

resolve-audit is a confirmed malicious npm package (MAL-2026-13987) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in resolve-audit (npm)

MAL-2026-13987

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall resolve-audit

What this malware does

[email protected] 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.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

86b902b4dc4c2187bb95548ed903dfea70ea626ba5450f031c2cb27b3639dd1c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for resolve-audit (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging resolve-audit across your stack and pipelines.
If you installed it — respond
Remove resolve-audit from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If resolve-audit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks resolve-audit before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. resolve-audit on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017677

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks resolve-audit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database