Which versions of pybanners are malicious?

The following PyPI versions of pybanners are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4. Treat any of these as compromised.

How do I remediate pybanners if I installed it?

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

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

Yes — pybanners is associated with the RLMA-2024-08862, 2024-07-blazesquad, RLUA-2026-00621 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 pybanners 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 pybanners (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pybanners across your stack and pipelines.

Malicious package

pybannersPyPI

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

MAL-2024-10112

Immediate action

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

pip uninstall pybanners

What this malware does

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-07-blazesquad

Reasons (based on the campaign):

infostealer
exfiltration-generic

Malicious versions

4 flagged

0.0.10.0.20.0.30.0.4

Indicators of compromise (SHA-256)

ee0e10720249b3532fed3e22a4b291888936bc4054f72ace7cee0f0733e7ad57

9a5ed7c99fe16990cf7f33ac81216d26d18bbe6a5022fda8a576d184aca96b4c

79f46da2dc3c934741de674c01635b94240ac249ba2d9cb9f7a89e0c8d80686a

645293395148605391670366a80da4635243ab356553ed86538b77ca85e10dc7

9774b370ff3e377360bac31a1858b9ce5f988e7c7552301a69c37655545beba4

bb49a4cd24a40591d3ff75bc054be3a9bda6435f8acf45031f6e19555ada8fb4

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

Campaign

RLMA-2024-088622024-07-blazesquadRLUA-2026-00621

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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