NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

wsh4_edunpm

Advisory published Updated

wsh4_edu is a confirmed malicious npm package (MAL-2026-11072) 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_edu (npm)

MAL-2026-11072
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall wsh4_edu

What this malware does

The package's postinstall hook runs index.js, which POSTs the installer's absolute filesystem path (via __filename with sendFullPath: true), Node.js version, platform, and architecture to a hardcoded Discord webhook at discord.com/api/webhooks/1530599209269465319/. The same beacon also fires when the module is required, since index.js is the package main. The absolute path typically embeds the local username and home directory, giving the operator of the webhook a host/identity fingerprint of every machine that installs the package. The webhook URL is split across two string literals and concatenated at call time to evade casual string scanning, and the destination is not caller-configurable. The package name and README self-describe as a typo/beacon experiment.

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

e68d4c62ae8440581c4400e1cdacb7877912eb23610e273432d18cea61574785
0757eee7b6324baca2e2b28261c7ff072c60d578c827a14c1fa54f690b1cd53a

Detection & response playbook

Backdoor / remote access
  1. Find it

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

  2. If you installed it — respond

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

  3. Did it already run?

    If wsh4_edu 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. wsh4_edu 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-011286

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

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

Explore

wsh4_edu (npm) malicious package — MAL-2026-11072 | O3 Security