# MAL-2026-5937: Malicious code in abuden21 (npm)


- **Type:** Malicious package
- **Package:** `abuden21` (npm)
- **Published:** 16 Jun 2026
- **Also known as:** GHSA-5wr3-rjvv-cgfj

## What is MAL-2026-5937?

MAL-2026-5937 is a malicious package in abuden21, published on 16 Jun 2026. 

### Official description

The tarball ships `auto-publish.sh`, which iterates a hardcoded list of ~90 unrelated package names (`imillegal1..N`, `ishowfeet*`, `nottuff*`, `abuden*`, `ratelimitsucks*`) and runs `npm publish --silent` for each, republishing the same payload under each name. The payload is a browser SPA (Mercury/Scramjet-style web proxy with a Lucide UI) plus heavily obfuscated JS bundles in `assets/*.js`. `package.json` has no `preinstall`/`install`/`postinstall` hooks and no `bin`; the declared `main` is a browser service worker (`sw.js`) that calls `importScripts`/`self` and throws immediately under Node, so `npm install abuden21` and `require('abuden21')` perform no code execution against the installer. The bundled `index.html` (and a duplicate inside `logo.svg`) registers click/keydown/touchstart handlers that open `https://abdct.com/` as a popunder on first user gesture when the SPA is served in a browser — monetisation of the web-proxy front-end, not installer-side harm. No credential reads, no outbound exfiltration on install, no RCE, no dropper. The behaviour of concern is namespace pollution: the same tarball is mass-published across many unrelated names to squat the npm namespace and ride traffic / typo'd installs. Routing to human review for namespace-abuse handling; this is not a direct supply-chain attack on installers but is an abuse pattern the registry/feed maintainers may want to act on.

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-5937?

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

## Sources

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

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