Which versions of randar303 are malicious?

The following PyPI versions of randar303 are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate randar303 if I installed it?

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

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

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

Malicious package

randar303PyPI

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

MAL-2025-47800

Immediate action

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

pip uninstall randar303

What this malware does

Importing the module downloads and executes widely recognized malware

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

Campaign: 2025-08-k7eel

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

d0167bf3026f31db275de740f3c9e0429736fd695f00accaffd16fc5ac382714

d92e64b3aca0ac226ddd7a05bc069341d003aa5dbcc1841d484cfcded99bde21

9ec94332277ac2c470647f10f1be8faace9da41d55c024e2d33c021ffe69f88d

26f2bc627a07c3d4e824b91a1f415c47f12725574c2629cb47c1f707d035f66a

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

Campaign

RLMA-2025-048072025-08-k7eelRLUA-2026-00683

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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