Which versions of node-procmetrics-data are malicious?

The following npm versions of node-procmetrics-data are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate node-procmetrics-data if I installed it?

node-procmetrics-data 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 node-procmetrics-data — how do I know if it already compromised me?

If node-procmetrics-data 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 node-procmetrics-data part of a known attack campaign?

Yes — node-procmetrics-data is associated with the IN-MAL-2026-010267 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 node-procmetrics-data 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 node-procmetrics-data (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-procmetrics-data across your stack and pipelines.

Malicious package

node-procmetrics-datanpm

Malicious code in node-procmetrics-data (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10464

Immediate action

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

npm uninstall node-procmetrics-data

What this malware does

[email protected] ships archive-sender.js which, at install/execution, tars the installer's root filesystem (excluding /proc, /sys, /dev, /tmp, /run) into /tmp/.archive_*.tar.gz, splits the archive into 200MB chunks, and publishes each chunk as a new version of node-procmetrics-data to the public npm registry. Authentication uses a hardcoded npm _authToken shipped in the package as a hex literal XORed with 0x5A at runtime, and the code writes this token into the installer's npm config via npm config set //registry.npmjs.org/:_authToken. The registry is abused as a covert exfiltration channel, and the shipped token is obfuscated to evade static credential scanners. The publish loop also programmatically writes package.json/data.bin and runs npm publish --access public, extending the attacker's registry footprint from the installer's machine.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

5ea7e26b73fb4fa21cdd545045f2a360a02d1013efe25cd6ab7aedb1fec72c9b

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 node-procmetrics-data (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-procmetrics-data across your stack and pipelines.
If you installed it — respond
node-procmetrics-data 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 node-procmetrics-data 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 node-procmetrics-data 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. node-procmetrics-data on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010267

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks node-procmetrics-data-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