Which versions of wsh4-nmp are malicious?

The following npm versions of wsh4-nmp are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate wsh4-nmp if I installed it?

wsh4-nmp establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed wsh4-nmp — how do I know if it already compromised me?

If wsh4-nmp 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.

Is wsh4-nmp part of a known attack campaign?

Yes — wsh4-nmp is associated with the GHSA-3wv5-4p57-2v5q, IN-MAL-2026-008291 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find wsh4-nmp across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for wsh4-nmp (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 wsh4-nmp across your stack and pipelines.

Malicious package

wsh4-nmpnpm

wsh4-nmp is a confirmed malicious npm package (MAL-2026-6792) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wsh4-nmp (npm)

MAL-2026-6792

Immediate action

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

npm uninstall wsh4-nmp

What this malware does

package.json declares scripts.postinstall = 'node index.js'. On install, index.js unconditionally POSTs installer-identifying data — the absolute __filename path (which reveals the OS username and home-directory layout), Node version, process.platform, and process.arch — to a hardcoded Discord webhook (discord.com/api/webhooks/1523336123319849031/...) controlled by the author. The beacon fires automatically at npm install with no consent, no opt-out, and no documented purpose disclosed to the installer. Package naming ('wsh4-nmp') and internal defaults ('whs4_typo') together with a README note about notifying on typos indicate the package is positioned as a typosquat probe whose function is to inform the author whenever an installer mistypes a target package name and pulls this one in.

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.

The OpenSSF Package Analysis project identified 'wsh4-nmp' @ 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)

e7eb1e1d0cace271eb14fb5f939e271fbe915ec9edd4413c85367c79296532ee

ae8d49fb38a00054e408984deccb85f6486ffa7aa61c31ad01402413143168d0

8f4958e0d564fad3efe079f48b02579eb052190951bc2ce2bf3d8bc067575c36

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for wsh4-nmp (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 wsh4-nmp across your stack and pipelines.
If you installed it — respond
wsh4-nmp establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If wsh4-nmp 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 wsh4-nmp 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

No. wsh4-nmp 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-3wv5-4p57-2v5qIN-MAL-2026-008291

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks wsh4-nmp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database