Which versions of xfoobar are malicious?

The following PyPI versions of xfoobar are flagged malicious: 0.0.5. Treat any of these as compromised.

How do I remediate xfoobar if I installed it?

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

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

Yes — xfoobar is associated with the 2026-06-anthropy, IN-MAL-2026-008481 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 xfoobar across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for xfoobar (version 0.0.5).

Malicious package

xfoobarPyPI

Advisory published Jun 8, 2026Updated Jul 8, 2026

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

Malicious code in xfoobar (PyPI)

MAL-2026-5335

Immediate action

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

pip uninstall xfoobar

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

During import, the package starts a reverse shell

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

Campaign: 2026-06-anthropy

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

1 flagged

0.0.5

Indicators of compromise (SHA-256)

a54c1c17d20a069af19c48751aada9e426bcbf55484c360cf21ac70f35d3d0dd

d82d6f4e4dba40d2e4677eb00c301bc816c8fe442704bdb9ed1f51a3d90e8f75

Detection & response playbook

Credential / info stealer

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

Campaign

2026-06-anthropyIN-MAL-2026-008481

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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