# MAL-2026-6094: Malicious code in metrics-probe-f256 (npm)


- **Type:** Malicious package
- **Package:** `metrics-probe-f256` (npm)
- **Published:** 18 Jun 2026
- **Also known as:** GHSA-wrx9-4534-jwh6

## What is MAL-2026-6094?

MAL-2026-6094 is a malicious package in metrics-probe-f256, published on 18 Jun 2026. 

### Official description

Package declares a postinstall lifecycle hook (`"postinstall": "node run.js"` in package.json) that executes run.js automatically on `npm install`. run.js imports child_process, os, https, and http; reads host identifiers via os.hostname() and os.platform() (run.js:194-195); and issues outbound POST requests (run.js:62, 63, 265) along with a GET (run.js:48). The shape — automatic install-time execution combined with host enumeration and outbound HTTP exfiltration primitives — matches the install-time host-reconnaissance / beacon pattern. The package name (metrics-probe-f256, with a random hex suffix) has no documented purpose consistent with running child processes and shipping host data outbound at install time.

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

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

## Sources

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

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