Which versions of @_wnpm/wnpm-cli are malicious?

The following npm versions of @_wnpm/wnpm-cli are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @_wnpm/wnpm-cli if I installed it?

Remove @_wnpm/wnpm-cli 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 @_wnpm/wnpm-cli — how do I know if it already compromised me?

If @_wnpm/wnpm-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.

How do I find @_wnpm/wnpm-cli across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @_wnpm/wnpm-cli (version 1.0.0).

Malicious package

@_wnpm/wnpm-clinpm

Advisory published Apr 2, 2026Updated Apr 7, 2026

@_wnpm/wnpm-cli is a confirmed malicious npm package (MAL-2026-2420) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @_wnpm/wnpm-cli (npm)

MAL-2026-2420

Immediate action

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

npm uninstall @_wnpm/wnpm-cli

What this malware does

The package @_wnpm/wnpm-cli was found to contain malicious code.

The OpenSSF Package Analysis project identified '@_wnpm/wnpm-cli' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

645ee324a93e8ebd1dbd9003186b577d1b6f76f0263f730950d26741cbc8e74c

9729c3c0a6c625f2d6cc79833205a4331647989fa84d85bdd158924af91020fd

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @_wnpm/wnpm-cli (version 1.0.0).
If you installed it — respond
Remove @_wnpm/wnpm-cli 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 @_wnpm/wnpm-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. @_wnpm/wnpm-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.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @_wnpm/wnpm-cli-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