# MAL-2026-6792: Malicious code in wsh4-nmp (npm)


- **Type:** Malicious package
- **Package:** `wsh4-nmp` (npm)
- **Published:** 5 Jul 2026
- **Also known as:** GHSA-3wv5-4p57-2v5q

## What is MAL-2026-6792?

MAL-2026-6792 is a malicious package in wsh4-nmp, published on 5 Jul 2026. 

### Official description

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.

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.

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.

## What should I do about MAL-2026-6792?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6792 is a malicious package: wsh4-nmp (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-6792/ (Markdown: https://insights.sbomify.com/MAL-2026-6792/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6792

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6792/
Summaries are generated and may contain mistakes; the official description above is the record.