Which versions of ebell are malicious?

The following PyPI versions of ebell are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate ebell if I installed it?

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

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

Yes — ebell is associated with the 2024-07-weaponized-golden 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 ebell across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ebell (version 0.1).

Malicious package

ebellPyPI

Advisory published Jul 28, 2024Updated Dec 12, 2025

ebell is a confirmed malicious PyPI package (MAL-2024-12263) that steals credentials and exfiltrates sensitive data (malicious version 0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ebell (PyPI)

MAL-2024-12263

Immediate action

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

pip uninstall ebell

What this malware does

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

Campaign: 2024-07-weaponized-golden

Reasons (based on the campaign):

files-exfiltration

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

60fc42702256b444142af81fe79448ac73539d1d8fdc0609859c81227e84c31c

e8e763e9a652876b90896b11102319e43569b39d2be23d4170446ded6a619b1f

050fd837cb4e44be711db0456302e4888789fdfb605320f156b238eec131831a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for ebell (version 0.1).
If you installed it — respond
ebell 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 ebell 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. ebell on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-07-weaponized-golden

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database