Which versions of emd-ext are malicious?

The following PyPI versions of emd-ext are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate emd-ext if I installed it?

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

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

Yes — emd-ext is associated with the GENERIC-hackerone-bugbounty 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 emd-ext across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for emd-ext (version 0.0.1).

Malicious package

emd-extPyPI

Advisory published Apr 10, 2026Updated Apr 10, 2026

emd-ext is a confirmed malicious PyPI package (MAL-2026-2532) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in emd-ext (PyPI)

MAL-2026-2532

Immediate action

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

pip uninstall emd-ext

What this malware does

Dependency confusion attempt. The user identifies themselves as a HackerOne user abusing the PyPI for the purpose of a bug bounty program. This package did not contain any exfiltration activity.

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-hackerone-bugbounty

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.
dependency-confusion

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8533b4542459021adb6dac35adcdda6eac7103c09dc091b7699c72d1d16101e2

Detection & response playbook

Credential / info stealer

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

Campaign

GENERIC-hackerone-bugbounty

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks emd-ext-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