Which versions of puffioner131 are malicious?

The following PyPI versions of puffioner131 are flagged malicious: 9999, 99999, 999999, 9999999, 99999999, 999999991, 999999999. Treat any of these as compromised.

How do I remediate puffioner131 if I installed it?

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

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

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

Malicious package

puffioner131PyPI

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

MAL-2024-8025

Immediate action

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

pip uninstall puffioner131

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.

The OpenSSF Package Analysis project identified 'puffioner131' @ 999999991 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

7 flagged

999999999999999999999999999999999999991999999999

Indicators of compromise (SHA-256)

3f949c1ed3b242666f9fceeb6adf4ec7105c6f257aaa86080d0fd154fa56a80f

d80eb997ae6841c572c88837dc6e194e2e20a5d12b31476f919b29f3b5931788

769ce8123d91c5655d14c6a2492df0bdec01d03ce14ade3edc125ef4c02b4ce7

03e7420ebe17c5b3feef69b274c7b6e57ed2e6913e19a561d7040e3b48e041a2

7cbefc979dbe0ce2160ad37ee4d538df237397846c71ff9249e5fc84a69eaae1

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

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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