Which versions of whs4_pnm are malicious?

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

How do I remediate whs4_pnm if I installed it?

whs4_pnm 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 whs4_pnm — how do I know if it already compromised me?

If whs4_pnm 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 whs4_pnm part of a known attack campaign?

Yes — whs4_pnm is associated with the GHSA-23v6-j5g5-7x9p, IN-MAL-2026-009225 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 whs4_pnm 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 whs4_pnm (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 whs4_pnm across your stack and pipelines.

Malicious package

whs4_pnmnpm

whs4_pnm is a confirmed malicious npm package (MAL-2026-6953) 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 whs4_pnm (npm)

MAL-2026-6953

Immediate action

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

npm uninstall whs4_pnm

What this malware does

The package declares a postinstall script (node index.js) that runs unconditionally on npm install. The script POSTs the absolute __filename path (which contains the installer's OS username via the home-directory prefix), the Node.js version, and the platform/architecture to a hardcoded Discord webhook at https://discord.com/api/webhooks/1523336123319849031/.... There is no opt-in, disclosure, or configuration option — every install silently transmits host-identifying data to an author-controlled endpoint. The package's own README and default internal packageName value (whs4_typo) indicate the package is positioned as a typo-target beacon, matching the typosquat-with-callback pattern where the attacker collects fingerprints of developers who mistype a legitimate package name.

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)

6c7538f81810e9802a2f2a45995000376e76177b2eb21d1c6e8aea63942a330d

47d72187d8b59a9a40cb8397d064bc7319b20e19ee7d48b870432bd96952b089

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 whs4_pnm (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 whs4_pnm across your stack and pipelines.
If you installed it — respond
whs4_pnm 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 whs4_pnm 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 whs4_pnm 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. whs4_pnm 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-23v6-j5g5-7x9pIN-MAL-2026-009225

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks whs4_pnm-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