Which versions of runtime-metrics-w7k2 are malicious?

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

How do I remediate runtime-metrics-w7k2 if I installed it?

runtime-metrics-w7k2 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 runtime-metrics-w7k2 — how do I know if it already compromised me?

If runtime-metrics-w7k2 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 runtime-metrics-w7k2 part of a known attack campaign?

Yes — runtime-metrics-w7k2 is associated with the IN-MAL-2026-006899, GHSA-65h4-xcqj-p428 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 runtime-metrics-w7k2 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 runtime-metrics-w7k2 (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 runtime-metrics-w7k2 across your stack and pipelines.

Malicious package

runtime-metrics-w7k2npm

runtime-metrics-w7k2 is a confirmed malicious npm package (MAL-2026-5992) 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 runtime-metrics-w7k2 (npm)

MAL-2026-5992

Immediate action

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

npm uninstall runtime-metrics-w7k2

What this malware does

Package declares a postinstall hook ("postinstall": "node run.js") that fires automatically on npm install. The tarball ships beacon scripts (beacon18.js, beacon_linux.js) that import child_process, os, and http, read host identifiers via os.hostname() / os.platform(), and issue outbound HTTP GET/POST requests carrying that data. The combination — automatic install-time execution, host enumeration, child_process reachability, and unsolicited outbound HTTP from an unknown low-reputation package named with a random suffix — matches a host-beacon / exfiltration shape with no legitimate library purpose. Installing this package on a developer or CI machine causes immediate disclosure of host metadata to an external endpoint and provides the publisher a foothold for follow-on commands.

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)

9c2062a3f2564ced7261d9b8be8a49e11117bd74ffe3e92aad6029c471921e2d

fd59b3ac5ad6ac2e38eec2f730d1a001953a3f342e47a28c96128fe814006877

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 runtime-metrics-w7k2 (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 runtime-metrics-w7k2 across your stack and pipelines.
If you installed it — respond
runtime-metrics-w7k2 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 runtime-metrics-w7k2 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 runtime-metrics-w7k2 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. runtime-metrics-w7k2 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-006899GHSA-65h4-xcqj-p428

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks runtime-metrics-w7k2-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