Which versions of blabutt are malicious?

The following PyPI versions of blabutt are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate blabutt if I installed it?

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

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

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

Malicious package

blabuttPyPI

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

MAL-2025-41625

Immediate action

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

pip uninstall blabutt

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

99.99.99

Indicators of compromise (SHA-256)

9c909b833d41e12e551e25101458db08801c0f6b3a414e7518028433cd5aa96c

a434a663424295555a75a21256264378a0c6928bea45b02a6d3f3f663ca53a0d

258dbe10b138b170391a1beecc464e618b85c47192f558a737105ef3525948ad

88f7c7a7c517bfaabbddaf88f9915252bd6fc3ab587bd50aeef5fdf6a1ace0d3

d93a253cb2a1e4972d4aa30395e9f0d1baf178f042903a1fee6ceeaa0657d3c2

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

Campaign

RLMA-2025-04116GENERIC-standard-pypi-install-pentestRLUA-2026-00150

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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