# MAL-2026-10216: Malicious code in node-sysmetrics (npm)


- **Type:** Malicious package
- **Package:** `node-sysmetrics` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-w2wx-f2m6-332m

## What is MAL-2026-10216?

MAL-2026-10216 is a malicious package in node-sysmetrics, published on 13 Jul 2026. 

### Official description

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.

## What should I do about MAL-2026-10216?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-10216 is a malicious package: node-sysmetrics (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-10216/ (Markdown: https://insights.sbomify.com/MAL-2026-10216/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-10216

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-10216/
Summaries are generated and may contain mistakes; the official description above is the record.