Which versions of whs4_nmp are malicious?

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

How do I remediate whs4_nmp if I installed it?

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

I already installed whs4_nmp — how do I know if it already compromised me?

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

Yes — whs4_nmp is associated with the GHSA-4fw4-5853-rqf8, IN-MAL-2026-009222, IN-MAL-2026-009223 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_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 whs4_nmp (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging whs4_nmp across your stack and pipelines.

Malicious package

whs4_nmpnpm

whs4_nmp is a confirmed malicious npm package (MAL-2026-6950) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in whs4_nmp (npm)

MAL-2026-6950

Immediate action

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

npm uninstall whs4_nmp

What this malware does

The package's postinstall script runs node index.js on install, which invokes reportLoadedFrom to POST installer-side data to a hardcoded Discord webhook (discord.com/api/webhooks/1523336123319849031/...). The transmitted payload includes the absolute filesystem path of the install location (which leaks the user's home directory / username), the Node.js version, and process.platform/process.arch. There is no disclosure, opt-in, or configuration surface — the destination is a fixed author-controlled channel. Package naming (whs4_nmp, internal default whs4_typo) and README framing (typo 발생시 안내합니다) indicate a dependency-confusion / typosquat probe designed to notify the author whenever a mistyped install lands on a real machine, harvesting host identifiers without consent.

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

05f2dab2e1b7ba48a8ac7e59bbaa32e72fe485b6ff9d28041becdde764394a06

2516b77223ed02019f2bbc420dc4e8c293a7339a4f8a1a858b9bf2dc0d54ae52

53a1fc3c42fcd64070dd50db1ed23a9f238bd10fea9bba087cb605f7419af28c

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for whs4_nmp (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging whs4_nmp across your stack and pipelines.
If you installed it — respond
whs4_nmp 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.
Did it already run?
If whs4_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 whs4_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. whs4_nmp on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4fw4-5853-rqf8IN-MAL-2026-009222IN-MAL-2026-009223

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks whs4_nmp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database