Which versions of dziplib are malicious?

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

How do I remediate dziplib if I installed it?

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

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

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

Malicious package

dziplibPyPI

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

MAL-2025-41668

Immediate action

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

pip uninstall dziplib

What this malware does

Package is runs an Infostealer targeting telegram and Discord credentials. Depending on version, the infostealer is either downloaded from an URL or embedded in the package

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

Campaign: 2025-08-dsidelib

Reasons (based on the campaign):

infostealer
Downloads and executes a remote malicious script.
exfiltration-browser-data
target:telegram

Malicious versions

2 flagged

1.0.01.2.0

Indicators of compromise (SHA-256)

a15abf754a3839e61f71765fbababcb97168daf556271559b9a26547c34236e4

88cc3f6bd64c51f340ea4ca5ab4b146ee766e7878aa25d747120164b08b54ca2

4330efb5db5e6d840d35a3da3ca6f6ad39fadff7e37e78745b9e092d365a7ded

f69972028d174de2c3398c841ffbdba99b4202698f0944d580915b16c778687d

f1d18f5f365d04a4905966f7e2e1758a23e4758b12d0ffc78a3249ca9d40ff3a

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 dziplib (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dziplib across your stack and pipelines.
If you installed it — respond
dziplib 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 dziplib 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 dziplib 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. dziplib on PyPI has been identified as a malicious package (versions 1.0.0, 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-041602025-08-dsidelibRLUA-2026-00286

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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