Which versions of rando0192490 are malicious?

The following PyPI versions of rando0192490 are flagged malicious: 0.1.9, 0.2.9. Treat any of these as compromised.

How do I remediate rando0192490 if I installed it?

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

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

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

Malicious package

rando0192490PyPI

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

MAL-2025-191655

Immediate action

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

pip uninstall rando0192490

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

2 flagged

0.1.90.2.9

Indicators of compromise (SHA-256)

86f20d60dac456eb102a81cf6ed81bf8944658c61bfd91d27f60b3a1902ea778

1c1c34ec73580f80a1d8681f7991a2366a2e268a823848a0d26555971b62c4e7

7d5805a2205690aef1009d3bec77df6c20de9d16fc8744b8e44f279bcc2ddab8

6ba4734802a6ce14dd3587cec96a89b030fc3298922d916beda800a48e34b828

8e5263e68eb37f432ae8b0ffdf86fc0e402b939209592fa8f20edaa712554dee

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

Campaign

RLMA-2025-056302025-10-wangzhou183RLUA-2026-00684

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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