Which versions of zabitog are malicious?

The following PyPI versions of zabitog are flagged malicious: 9.0.1. Treat any of these as compromised.

How do I remediate zabitog if I installed it?

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

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

Yes — zabitog is associated with the 2026-02-zabitmajeed00, RLMA-2026-00944 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 zabitog across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zabitog (version 9.0.1).

Malicious package

zabitogPyPI

Advisory published Feb 2, 2026Updated Mar 19, 2026

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

Malicious code in zabitog (PyPI)

MAL-2026-654

Immediate action

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

pip uninstall zabitog

What this malware does

Obfuscated code is used to hide exfiltration of basic data (hostname, etc.).

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: 2026-02-zabitmajeed00

Reasons (based on the campaign):

obfuscation
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

9.0.1

Indicators of compromise (SHA-256)

23d4c7f55266f10f23ddf4a743bb4222b920c0e7f4472c1572a51831a3d1f247

49586d4a2112fa76c895f00292bb344acbcd62c82eea301083fdbee5483a5eb4

Detection & response playbook

Credential / info stealer

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

Campaign

2026-02-zabitmajeed00RLMA-2026-00944

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter
ReversingLabs · finder

Detect & block this

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