# MAL-2026-6950: Malicious code in whs4_nmp (npm)


- **Type:** Malicious package
- **Package:** `whs4_nmp` (npm)
- **Published:** 7 Jul 2026
- **Also known as:** GHSA-4fw4-5853-rqf8

## What is MAL-2026-6950?

MAL-2026-6950 is a malicious package in whs4_nmp, published on 7 Jul 2026. 

### Official description

The package's `postinstall` script runs `node index.js` on install, which invokes `reportLoadedFrom` to POST installer-side data to a hardcoded Discord webhook (`discord.com/api/webhooks/1523336123319849031/...`). The transmitted payload includes the absolute filesystem path of the install location (which leaks the user's home directory / username), the Node.js version, and `process.platform`/`process.arch`. There is no disclosure, opt-in, or configuration surface — the destination is a fixed author-controlled channel. Package naming (`whs4_nmp`, internal default `whs4_typo`) and README framing (`typo 발생시 안내합니다`) indicate a dependency-confusion / typosquat probe designed to notify the author whenever a mistyped install lands on a real machine, harvesting host identifiers without 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.

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

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-6950 is a malicious package: whs4_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-6950/ (Markdown: https://insights.sbomify.com/MAL-2026-6950/index.md)
```

## Sources

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

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