Which versions of node-sysmetrics are malicious?

The following npm versions of node-sysmetrics are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate node-sysmetrics if I installed it?

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

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

Yes — node-sysmetrics is associated with the GHSA-w2wx-f2m6-332m, IN-MAL-2026-009787, IN-MAL-2026-009786 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-sysmetrics 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-sysmetrics (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-sysmetrics across your stack and pipelines.

Malicious package

node-sysmetricsnpm

node-sysmetrics is a confirmed malicious npm package (MAL-2026-10216) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-sysmetrics (npm)

MAL-2026-10216

Immediate action

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

npm uninstall node-sysmetrics

What this malware does

On npm install, install.js executes as a postinstall script and drops a detached background Node process at /tmp/.sysm-agent.js that persists after installation. The agent enters an infinite polling loop against registry.npmjs.org, reading the package's own dist-tags for base64-encoded commands, decoding them, and executing them via bash -c on the installer's host. Command output is then base64-encoded and exfiltrated by publishing throwaway public npm packages containing the encoded output in the description field, using a hardcoded npm auth token embedded in install.js. The same token is written into the installer's global npm config at ~/.npmrc via npm config set //registry.npmjs.org/:_authToken, hijacking the installer's package manager credentials. Base64 encoding is used on both the inbound command channel and the outbound result channel to evade casual inspection of registry metadata.

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

00b72eed54e4dba21b0eb58a9b9f0fe238ee5b3cc90a04c031e539d4a69050ea

25414e99686f31b6344740f4d65d66fef96777b641d2ae1d46171f9a2835ce27

e624a951ebd9352b2b8d47bf80d418a01674640ec2d2b2592f00bb446f110c68

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

Campaign

GHSA-w2wx-f2m6-332mIN-MAL-2026-009787IN-MAL-2026-009786

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks node-sysmetrics-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