wsh4_npm
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-6h38-53x2-5jhm
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in wsh4_npm (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (9b6c0b02642cf1c4c0fe420fd03c0c129c21a544144878df4833373da1b98aab)
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.
Source: ghsa-malware (c8133756ff7c30e9051c8fa79fec692e9427a3d41f97eed4e031d2e7d0a25170)
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.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0