# MAL-2026-14361: Malicious code in stillm4ddpocs-demo-gadget (npm)


- **Type:** Malicious package
- **Package:** `stillm4ddpocs-demo-gadget` (npm)
- **Published:** 22 Aug 2026

## What is MAL-2026-14361?

MAL-2026-14361 is a malicious package in stillm4ddpocs-demo-gadget, published on 22 Aug 2026. 

### Official description

On npm install, the declared preinstall script runs index.js, which collects the installer's hostname, OS username, home directory, cwd (INIT_CWD of the consuming project), local IPv4 address, egress public IP (fetched from api.ipify.org, icanhazip.com, and ifconfig.me), DNS resolver information, and the parent project's package.json fields (name, author, repository, homepage). The collected data is transmitted to the hardcoded third-party callback host da51rv0hb2uc72tg4gvgdepinjcalbk1.oast.fun via both DNS queries (hex-chunked subdomain lookups) and HTTPS POST to /poc/<uuid>. The package name and version pattern are consistent with a dependency-confusion lure targeting an internal scope; the beacon fires automatically at install time without any caller opt-in. Although the author metadata self-labels this as an authorized proof-of-concept, the code performs the full exploitation shape (auto-exec on install, installer-identifier collection, egress to an attacker-controlled callback) against anyone who resolves this public name.

The OpenSSF Package Analysis project identified 'stillm4ddpocs-demo-gadget' @ 999.9.10 (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-14361?

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

## Sources

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

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