Which versions of puan4 are malicious?

The following PyPI versions of puan4 are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate puan4 if I installed it?

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

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

Yes — puan4 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 puan4 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 puan4 (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging puan4 across your stack and pipelines.

Malicious package

puan4PyPI

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

MAL-2026-3244

Immediate action

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

pip uninstall puan4

What this malware does

During import, package automatically starts a connection to a C2 server, exfiltrates information about the host and data like sensitive files and browsers' data.

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

1 flagged

1.0.3

Indicators of compromise (SHA-256)

6be2e7028440f68ad3621664d195d72288e6a1d8658f16a421f3ec52d63d6f7a

a1ede45ed3cdcf9c9f386d9b290d05590e0a8efcc7c0c5e338fd3bd6c0a24aeb

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 puan4 (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging puan4 across your stack and pipelines.
If you installed it — respond
puan4 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 puan4 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 puan4 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. puan4 on PyPI has been identified as a malicious package (version 1.0.3 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 puan4-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