Which versions of zlibxjson are malicious?

The following PyPI versions of zlibxjson are flagged malicious: 8.1, 8.2. Treat any of these as compromised.

How do I remediate zlibxjson if I installed it?

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

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

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

Malicious package

zlibxjsonPyPI

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

MAL-2024-10220

Immediate action

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

pip uninstall zlibxjson

What this malware does

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

Campaign: zlibxjson-discord-cookies

Reasons (based on the campaign):

infostealer

Malicious versions

2 flagged

8.18.2

Indicators of compromise (SHA-256)

83a74dd2a53c3a078e47bf329f0d116760cb1cce293fa36c4a9edf45c15b9138

51452ca037e090ebd2ac2ba19a0118cfe7a7b8a4f553c75df6193cb04dd2c3dc

7066166aef73a74278d8bf23450a89f6a42d22c8fac20660bc5275868b92d211

35640be665450143a4a26c497d0b25882befa96327f12e8758587ecf5f249bc7

3968164b2bc735ea7db194e0f59fe841b20831be557744f57fc4643141beec48

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

Campaign

RLMA-2024-09580zlibxjson-discord-cookiesRLUA-2026-00950

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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