Which versions of cheezokdi10 are malicious?

The following PyPI versions of cheezokdi10 are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate cheezokdi10 if I installed it?

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

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

Yes — cheezokdi10 is associated with the RLMA-2025-05589, 2025-10-wangzhou183, RLUA-2026-00188 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 cheezokdi10 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 cheezokdi10 (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cheezokdi10 across your stack and pipelines.

Malicious package

cheezokdi10PyPI

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

MAL-2025-191621

Immediate action

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

pip uninstall cheezokdi10

What this malware does

Packages that either reports home installation, simulate malicious activity or imitate Roblox API wrapper.

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-10-wangzhou183

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

9870ee7cac2eb115839205c9a52f5e08d22f1ab5bf9221b2e7317b9d2d963348

c610176cf3e6d56a05b668fb04d06f57189a6c3034e3a1910666b8d5cf717eb2

dd24bfc0e91de2e63355bbbcc13bd07d47a58a3925d15cfc522a1ea407c2a945

21a82c41b995f5856f0f357e6dfce46769104a3a179cd8285d7f10c5fc076c13

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

Campaign

RLMA-2025-055892025-10-wangzhou183RLUA-2026-00188

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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