Which versions of caixaequ2ahzoop are malicious?

The following PyPI versions of caixaequ2ahzoop are flagged malicious: 2.0.0, 2.0.1. Treat any of these as compromised.

How do I remediate caixaequ2ahzoop if I installed it?

Remove caixaequ2ahzoop from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed caixaequ2ahzoop — how do I know if it already compromised me?

If caixaequ2ahzoop was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is caixaequ2ahzoop part of a known attack campaign?

Yes — caixaequ2ahzoop is associated with the 2025-05-caixaequ2ahzoop 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 caixaequ2ahzoop across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for caixaequ2ahzoop (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging caixaequ2ahzoop across your stack and pipelines.

Malicious package

caixaequ2ahzoopPyPI

Malicious code in caixaequ2ahzoop (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-4526

Immediate action

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

pip uninstall caixaequ2ahzoop

What this malware does

Obfuscated code gets a command from the remote target and executes it. At the time of the test, it was just "whoami". Thus, it's rather just an experiment

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: 2025-05-caixaequ2ahzoop

Reasons (based on the campaign):

obfuscation
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

The OpenSSF Package Analysis project identified 'caixaequ2ahzoop' @ 2.0.0 (pypi) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

2.0.02.0.1

Indicators of compromise (SHA-256)

82f9967b944983f117b085820df45222a6d7e6cfd130081af546f52071f9e21d

d1dea941c248c1d64b68f80e89ff01f645683d7b5d8ec260709e4f43191fb222

9545f83711d0d85c5530e296ec6ef300f8785f643cdc77efc3ca7c7e2a486002

da1d699d5d12de135ae0da4180622e30084a77fd76ee5cd36fe5667ce14c4bbe

8bc44605b08b6de7f77947a3a750f4b38145f3f1e6bd9075d1cd269489d4f9c4

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for caixaequ2ahzoop (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging caixaequ2ahzoop across your stack and pipelines.
If you installed it — respond
Remove caixaequ2ahzoop from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If caixaequ2ahzoop was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks caixaequ2ahzoop before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. caixaequ2ahzoop on PyPI has been identified as a malicious package (versions 2.0.0, 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-05-caixaequ2ahzoop

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks caixaequ2ahzoop-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring