node-sysmetricsnpm
Advisory published Updated
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for node-sysmetrics (2 malicious versions).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
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.