Which versions of pie-docs are malicious?

The following npm versions of pie-docs are flagged malicious: 1.0.0, 4.31.0. Treat any of these as compromised.

How do I remediate pie-docs if I installed it?

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

If pie-docs 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.

Is pie-docs part of a known attack campaign?

Yes — pie-docs is associated with the GHSA-qv69-65wh-qgf6 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 pie-docs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pie-docs (2 malicious versions).

Malicious package

pie-docsnpm

Advisory published Apr 30, 2025Updated Aug 17, 2026

pie-docs is a confirmed malicious npm package (MAL-2025-3660) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 4.31.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pie-docs (npm)

MAL-2025-3660

Immediate action

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

npm uninstall pie-docs

What this malware does

This package steals IP address and sent it to C&C server in preinstall hook.

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.04.31.0

Indicators of compromise (SHA-256)

6326ffe9d39e0d889a1a93b2faf51b274055e4a9f12f3596cdca2f85098245d3

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pie-docs (2 malicious versions).
If you installed it — respond
pie-docs 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 pie-docs 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

No. pie-docs on npm has been identified as a malicious package (versions 1.0.0, 4.31.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qv69-65wh-qgf6

References

github.com

Credits

Safedep · finder

Detect & block this

O3 blocks pie-docs-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