Which versions of pyunzip are malicious?

The following PyPI versions of pyunzip are flagged malicious: 0.0.1, 0.0.2, 0.0.4. Treat any of these as compromised.

How do I remediate pyunzip if I installed it?

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

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

Yes — pyunzip is associated with the RLMA-2024-09088, 2024-08-koalabuilder, RLUA-2026-00673 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 pyunzip 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 pyunzip (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyunzip across your stack and pipelines.

Malicious package

pyunzipPyPI

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

MAL-2024-10148

Immediate action

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

pip uninstall pyunzip

What this malware does

Packages downloads remote executable. The final behaviour is unknown, but starts with bypassing UAC and other security controls. Some package clones are obfuscated.

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

Campaign: 2024-08-koalabuilder

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation

Malicious versions

3 flagged

0.0.10.0.20.0.4

Indicators of compromise (SHA-256)

bd2e30d1ab22ee419d7721b5a633f4e5958ab8fd347b243361a17706e6924fd7

473172d8f1c8c8f198d855ddb970266963228355d4068a487909a87b082a581c

e671073274c02d02bdf77f71684ba7a0a854a30cdd671ea431ff5b4ea6d54add

8582d66c7b17abedaa934105a14863fb476ad16b05476a49112ea779411ba701

176d1402de0a259aaf6637990ab40311029e85116e675d493eea57388eb666de

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pyunzip (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyunzip across your stack and pipelines.
If you installed it — respond
pyunzip 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 pyunzip 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 pyunzip 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. pyunzip on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-090882024-08-koalabuilderRLUA-2026-00673

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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