check-auditnpm
check-audit is a confirmed malicious npm package (MAL-2026-13976) 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 check-audit (npm)
What this malware does
[email protected] is an otherwise empty package (no author, no description, no meaningful code) whose only effect on install is to pull a dependency named ltidisafe from an arbitrary Google Cloud Storage URL: https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.5.tgz. This URL is not the npm registry and is not tied to any declared publisher of check-audit. The tarball contents are mutable and bypass registry-side scanning; whatever code and lifecycle scripts it ships execute in the installer's node_modules on npm install. The version number (99.9.1) and hollow package contents are consistent with a lure/dropper whose sole purpose is to pull attacker-controllable code into the dependency tree at install time.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for check-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 check-audit across your stack and pipelines.
If you installed it — respond
Remove check-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 check-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 check-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks check-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.