Which versions of pinstatsd are malicious?

Every published version of pinstatsd on npm is considered malicious. Remove the package entirely.

How do I remediate pinstatsd if I installed it?

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

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

Yes — pinstatsd is associated with the GHSA-mwj4-gvm3-8rmh 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 pinstatsd 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 pinstatsd (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pinstatsd across your stack and pipelines.

Malicious package

pinstatsdnpm

Malicious code in pinstatsd (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2654

Immediate action

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

npm uninstall pinstatsd

What this malware does

Package is malware due to data exfiltration to multiple domains via DNS and HTTPS, along with a suspicious preinstall script.

The package pinstatsd was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

517d062bd44f74638ecf3bf62cbbbd86d25313b0f1938e79a068c9ad5b60370b

1b13ae52dde0a4efddd6d12bc4795b77da5433cb750b4ddb852f1aca27ea457e

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

Campaign

GHSA-mwj4-gvm3-8rmh

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks pinstatsd-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