Which versions of metrics-probe-f256 are malicious?

The following npm versions of metrics-probe-f256 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate metrics-probe-f256 if I installed it?

metrics-probe-f256 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed metrics-probe-f256 — how do I know if it already compromised me?

If metrics-probe-f256 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is metrics-probe-f256 part of a known attack campaign?

Yes — metrics-probe-f256 is associated with the IN-MAL-2026-006967, GHSA-wrx9-4534-jwh6 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find metrics-probe-f256 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for metrics-probe-f256 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging metrics-probe-f256 across your stack and pipelines.

Malicious package

metrics-probe-f256npm

metrics-probe-f256 is a confirmed malicious npm package (MAL-2026-6094) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in metrics-probe-f256 (npm)

MAL-2026-6094

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall metrics-probe-f256

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3fdf2b93d50f09ea1b087bdc33578fedec5483e75c7a9acd61355cc02f9f7ec0

79ab0bc35fa37afe4238ba6724b1c55b0daa1139fb6c04becc1d2ff3014c12a4

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for metrics-probe-f256 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging metrics-probe-f256 across your stack and pipelines.
If you installed it — respond
metrics-probe-f256 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If metrics-probe-f256 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks metrics-probe-f256 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. metrics-probe-f256 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006967GHSA-wrx9-4534-jwh6

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks metrics-probe-f256-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database