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?

Remove metrics-probe-f256 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

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.

Can O3 Security detect metrics-probe-f256 in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking metrics-probe-f256 and packages like it before any post-install script runs.

Malicious package

metrics-probe-f256npm

Malicious code in metrics-probe-f256 (npm) Remove it immediately and rotate any exposed credentials.

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

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

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection