Which versions of buffparser are malicious?

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

How do I remediate buffparser if I installed it?

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

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

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

Search your lockfiles and build artifacts for buffparser (version 1.0.0).

Malicious package

buffparserPyPI

Advisory published Apr 30, 2026Updated Apr 30, 2026

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

Malicious code in buffparser (PyPI)

MAL-2026-3203

Immediate action

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

pip uninstall buffparser

What this malware does

Described as a utility for gaming, the code starts a reverse shell when using the exposed alledegdly parsing function.

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

Campaign: 2026-04-buffparser

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.
action-hidden-in-lib-usage

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5cc891132b1216e9093bcdd4581373dc7f750f700c82347c28bd1dff079261d8

Detection & response playbook

Credential / info stealer

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

Campaign

2026-04-buffparser

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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