Which versions of puffionerlolpo2131 are malicious?

The following PyPI versions of puffionerlolpo2131 are flagged malicious: 1. Treat any of these as compromised.

How do I remediate puffionerlolpo2131 if I installed it?

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

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

Yes — puffionerlolpo2131 is associated with the RLMA-2024-11122, GENERIC-standard-pypi-install-pentest, RLUA-2026-00615 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 puffionerlolpo2131 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 puffionerlolpo2131 (version 1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging puffionerlolpo2131 across your stack and pipelines.

Malicious package

puffionerlolpo2131PyPI

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

MAL-2024-11665

Immediate action

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

pip uninstall puffionerlolpo2131

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

Indicators of compromise (SHA-256)

efb2b12dbced245abccc98efd14e08d841f2d5049e2fe45ce504ed1d8eca2fbc

edfd0d3ca328140b279be30ee61edc10a4f4141b522fb8b4b0262d76c40044fe

80a02e95092a88f93b35471d27c9b913bd00100f9d34aa5b97983a717f4ce740

c38ceefbde027c62c3dcb8d15a33c8534fd1f4f06392317b6e168d8725a42b2b

b61c4e346779b663868ed1e5d7188d41a0086c97575954e766a84a9d6e0549a1

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

Campaign

RLMA-2024-11122GENERIC-standard-pypi-install-pentestRLUA-2026-00615

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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