Which versions of puan31 are malicious?

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

How do I remediate puan31 if I installed it?

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

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

Yes — puan31 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 puan31 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for puan31 (2 malicious versions).

Malicious package

puan31PyPI

Advisory published May 3, 2026Updated May 3, 2026

puan31 is a confirmed malicious PyPI package (MAL-2026-3251) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in puan31 (PyPI)

MAL-2026-3251

Immediate action

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

pip uninstall puan31

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.
exfiltration-credentials
rat

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

27d04731b8fc3968b624ec2435d48b09d1afffb46fefb44745c2c8ff31bf4855

Detection & response playbook

Credential / info stealer

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