Which versions of bundyfed are malicious?

The following PyPI versions of bundyfed are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate bundyfed if I installed it?

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

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

Yes — bundyfed is associated with the 2026-11-bundyfed 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 bundyfed across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bundyfed (2 malicious versions).

Malicious package

bundyfedPyPI

Advisory published Nov 8, 2026Updated Nov 8, 2026

bundyfed is a confirmed malicious PyPI package (MAL-2026-18770) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bundyfed (PyPI)

MAL-2026-18770

Immediate action

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

pip uninstall bundyfed

What this malware does

During installation, the package downloads a malicious executable holding an infostealer.

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

Campaign: 2026-11-bundyfed

Reasons (based on the campaign):

Downloads and executes a remote executable.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

81b2cc96166cfebf7a2fb72d280ca06f5b9c4c9c735f6aee4beceafbce5430de

Detection & response playbook

Credential / info stealer

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

Campaign

2026-11-bundyfed

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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