Which versions of ebe are malicious?

The following PyPI versions of ebe are flagged malicious: 8.0.5. Treat any of these as compromised.

How do I remediate ebe if I installed it?

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

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

Yes — ebe 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 ebe 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 ebe (version 8.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ebe across your stack and pipelines.

Malicious package

ebePyPI

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

MAL-2024-12262

Immediate action

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

pip uninstall ebe

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

8.0.5

Indicators of compromise (SHA-256)

c73f63e52cc5b3b90e5646ff1d59d6d48c07398b8a7f377e301cade1a1f68741

7f86097ff84bdd8007ecb73c8e4a3d412500e503469684998f78fd39b14e51d5

284183cbd28541db57e3ff21108ceec52a8ac23dbd2f3849c89692b641c6e664

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 ebe (version 8.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ebe across your stack and pipelines.
If you installed it — respond
ebe 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 ebe 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 ebe 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. ebe on PyPI has been identified as a malicious package (version 8.0.5 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 ebe-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