Which versions of wsh4_npm are malicious?

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

How do I remediate wsh4_npm if I installed it?

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

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

Yes — wsh4_npm is associated with the GHSA-6h38-53x2-5jhm, IN-MAL-2026-008290 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_npm 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_npm (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_npm across your stack and pipelines.

Malicious package

wsh4_npmnpm

wsh4_npm is a confirmed malicious npm package (MAL-2026-6954) 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_npm (npm)

MAL-2026-6954

Immediate action

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

npm uninstall wsh4_npm

What this malware does

On npm install, the package's postinstall hook (scripts.postinstall: node index.js) auto-executes index.js, which builds a payload containing the absolute installation path (which reveals the installer's OS username via the home directory prefix), the Node.js version, platform, and architecture, and POSTs it to a hardcoded Discord webhook at discord.com/api/webhooks/1523336123319849031/... controlled by the author. The package's default internal name is whs4_typo and its README states it is intended to notify on typo installs; there is no legitimate functionality beyond the beacon. This is a typosquat-style reconnaissance beacon: the attacker gains identifying information about developers/build systems that mistype a target package name, on every install, with no user 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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

c8133756ff7c30e9051c8fa79fec692e9427a3d41f97eed4e031d2e7d0a25170

9b6c0b02642cf1c4c0fe420fd03c0c129c21a544144878df4833373da1b98aab

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_npm (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_npm across your stack and pipelines.
If you installed it — respond
wsh4_npm 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_npm 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_npm 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_npm 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-6h38-53x2-5jhmIN-MAL-2026-008290

References

Credits

Amazon Inspector · finder

Detect & block this

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