Which versions of whs4_ued are malicious?

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

How do I remediate whs4_ued if I installed it?

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

If whs4_ued 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.

Is whs4_ued part of a known attack campaign?

Yes — whs4_ued is associated with the IN-MAL-2026-017375 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_ued across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for whs4_ued (version 1.0.0).

Malicious package

whs4_uednpm

Advisory published Aug 11, 2026Updated Aug 11, 2026

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

MAL-2026-13743

Immediate action

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

npm uninstall whs4_ued

What this malware does

On npm install, the package's postinstall hook runs node index.js, which POSTs installer host information — the absolute path of the package file (leaking the OS username and home directory layout), Node.js version, platform, and architecture — to a hardcoded Discord webhook at discord.com/api/webhooks/1530599209269465319/. The webhook token is assembled via string concatenation at the call site to evade naive string matching. The destination is attacker-controlled and unrelated to the package's stated educational typo-catcher purpose, and there is no consent gate.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6be723a2156cdb77cc97a0afb9ee15e4d50928a1924cd6cde69bcaacf2707a8b

Detection & response playbook

Malicious package

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

IN-MAL-2026-017375

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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