Which versions of phasedibd are malicious?

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

How do I remediate phasedibd if I installed it?

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

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

Yes — phasedibd 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 phasedibd across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for phasedibd (version 0.0.1).

Malicious package

phasedibdPyPI

Advisory published Apr 10, 2026Updated Apr 10, 2026

phasedibd is a confirmed malicious PyPI package (MAL-2026-2533) 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 phasedibd (PyPI)

MAL-2026-2533

Immediate action

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

pip uninstall phasedibd

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)

8d514af72edb0054d9c5ff73f59a8517927dc660a5a58c8a03baf8abc5b22365

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for phasedibd (version 0.0.1).
If you installed it — respond
phasedibd 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 phasedibd 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. phasedibd 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 phasedibd-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