NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

credential-verification-clinpm

Advisory published Updated

credential-verification-cli is a confirmed malicious npm package (MAL-2026-4235) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in credential-verification-cli (npm)

MAL-2026-4235
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall credential-verification-cli

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

1 flagged
1.0.0

Indicators of compromise (SHA-256)

0342bd009d8ae24ecb515cd312610989610bb7886ca5a28cce25d7a41265c9f8
ebec51669e1875ebdcbe28040480db123cd5b42e4dbd4229b534a6e07e41b593

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for credential-verification-cli (version 1.0.0).

  2. 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.

  3. Did it already run?

    If credential-verification-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

GHSA-c7hj-r4xg-q237IN-MAL-2026-004115

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.

Explore

credential-verification-cli (npm) malicious package — MAL-2026-4235 | O3 Security