Which versions of piepunk are malicious?

The following PyPI versions of piepunk are flagged malicious: 6.9.0, 6.9.1, 6.9.3. Treat any of these as compromised.

How do I remediate piepunk if I installed it?

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

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

Yes — piepunk is associated with the 2024-12-piepunk 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 piepunk 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 piepunk (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging piepunk across your stack and pipelines.

Malicious package

piepunkPyPI

Malicious code in piepunk (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12322

Immediate action

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

pip uninstall piepunk

What this malware does

This is a clone of "pymunk" package. In the space.py file there is a code that attempts to exfiltrate data from the Discord client during initialization. L101:129

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-12-piepunk

Reasons (based on the campaign):

exfiltration-generic
infostealer
clones-real-package
action-hidden-in-lib-usage

Malicious versions

3 flagged

6.9.06.9.16.9.3

Indicators of compromise (SHA-256)

2150fce5d17537377c902711664078bdb143099946e2105018a4a43fedd84d87

40c9660a52e99412daf32818f5263ad562bf43281984b9676aa93874912132be

9c4476825aac01ea124ed0d6dede2b4183df8485af01036d7c35e19e4b3982a9

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

Campaign

2024-12-piepunk

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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