Which versions of common-cli-utils are malicious?

The following npm versions of common-cli-utils are flagged malicious: 0.0.0. Treat any of these as compromised.

How do I remediate common-cli-utils if I installed it?

Remove common-cli-utils 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 common-cli-utils — how do I know if it already compromised me?

If common-cli-utils 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.

How do I find common-cli-utils across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for common-cli-utils (version 0.0.0).

Malicious package

common-cli-utilsnpm

Advisory published Jan 1, 2026Updated Jan 2, 2026

common-cli-utils is a confirmed malicious npm package (MAL-2026-2) that executes malicious code on install (malicious version 0.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in common-cli-utils (npm)

MAL-2026-2

Immediate action

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

npm uninstall common-cli-utils

What this malware does

The package common-cli-utils was found to contain malicious code.

The OpenSSF Package Analysis project identified 'common-cli-utils' @ 0.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.0.0

Indicators of compromise (SHA-256)

952520ed514687905c66c0036c4f27625d6465d0a75d333d7b07353d3ba55faa

1b4c7bdeaa334d938afac649a1c3195ff47bf6fef18168e78b61ad22c6252450

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for common-cli-utils (version 0.0.0).
If you installed it — respond
Remove common-cli-utils 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 common-cli-utils 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. common-cli-utils on npm has been identified as a malicious package (version 0.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks common-cli-utils-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