Which versions of puan3 are malicious?

The following PyPI versions of puan3 are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate puan3 if I installed it?

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

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

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

Malicious package

puan3PyPI

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

MAL-2026-3243

Immediate action

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

pip uninstall puan3

What this malware does

During import, package automatically starts a connection to a C2 server, exfiltrates information about the host and data like the browser's history and sensitive files, and then waits for remote commands to execute.

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

Campaign: 2026-05-puan3

Reasons (based on the campaign):

exfiltration-generic
exfiltration-browser-data
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
rat
exfiltration-credentials

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

531ab02814e67f81e5c82fb57b72d59c3972d0975932f6e9d00ea680040e9a13

d4704e51813049248eccf78133b3ccc8816cfebb30555fa2adf67e99534349d4

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

Campaign

2026-05-puan3

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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