wsh4-nmp

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (8f4958e0d564fad3efe079f48b02579eb052190951bc2ce2bf3d8bc067575c36)
package.json declares scripts.postinstall = 'node index.js'. On install, index.js unconditionally POSTs installer-identifying data — the absolute __filename path (which reveals the OS username and home-directory layout), Node version, process.platform, and process.arch — to a hardcoded Discord webhook (discord.com/api/webhooks/1523336123319849031/...) controlled by the author. The beacon fires automatically at `npm install` with no consent, no opt-out, and no documented purpose disclosed to the installer. Package naming ('wsh4-nmp') and internal defaults ('whs4_typo') together with a README note about notifying on typos indicate the package is positioned as a typosquat probe whose function is to inform the author whenever an installer mistypes a target package name and pulls this one in.

## Source: ghsa-malware (ae8d49fb38a00054e408984deccb85f6486ffa7aa61c31ad01402413143168d0)
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.

## Source: ossf-package-analysis (e7eb1e1d0cace271eb14fb5f939e271fbe915ec9edd4413c85367c79296532ee)
The OpenSSF Package Analysis project identified 'wsh4-nmp' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

Compromised versions (1)

• 1.0.0

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.