Which versions of bananaholder are malicious?

The following PyPI versions of bananaholder are flagged malicious: 0.0.110. Treat any of these as compromised.

How do I remediate bananaholder if I installed it?

Remove bananaholder from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed bananaholder — how do I know if it already compromised me?

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

Yes — bananaholder is associated with the 2024-08-install-from-webhook 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 bananaholder across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bananaholder (version 0.0.110).

Malicious package

bananaholderPyPI

Advisory published Aug 22, 2024Updated Dec 12, 2025

bananaholder is a confirmed malicious PyPI package (MAL-2024-12213) that executes malicious code on install (malicious version 0.0.110). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bananaholder (PyPI)

MAL-2024-12213

Immediate action

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

pip uninstall bananaholder

What this malware does

A dependency is declared as installable from a webhook service, demonstrating a possibility to inject malicious dependency.

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: 2024-08-install-from-webhook

Reasons (based on the campaign):

The malicious code is intentionally included in a dependency of the package

Malicious versions

1 flagged

0.0.110

Indicators of compromise (SHA-256)

15ac0475854dce25a3f13309a2c6aed420cba9e2e2b1f600e325801236d4a20d

75eb68c36b36e5abf8c54609a124590a23d388ef04d2825da3bd83f8e90c7f46

0ecb4648bc0f306ce53ca0f7a7068af4b8095e564f949dc1f66cf856d9867869

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bananaholder (version 0.0.110).
If you installed it — respond
Remove bananaholder from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If bananaholder 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. bananaholder on PyPI has been identified as a malicious package (version 0.0.110 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-08-install-from-webhook

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks bananaholder-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database