Which versions of robloxextra are malicious?

The following PyPI versions of robloxextra are flagged malicious: 0.1, 0.2, 0.3, 0.4, 0.6, 0.7, 0.8. Treat any of these as compromised.

How do I remediate robloxextra if I installed it?

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

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

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

Malicious package

robloxextraPyPI

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

MAL-2025-6578

Immediate action

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

pip uninstall robloxextra

What this malware does

Importing the module starts downloading multiple stages of obfuscated code, that e.g. adds itself to autostart.

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

Campaign: 2025-06-robloxextra

Reasons (based on the campaign):

typosquatting
Downloads and executes a remote malicious script.
obfuscation
peristence-autorun

Malicious versions

7 flagged

0.10.20.30.40.60.70.8

Indicators of compromise (SHA-256)

0ae2bd4a4f0447141edfabbeec920bbc131de79d7389d2acf951644d61fd2bc5

eb617e0ec6530627e92c7a6673d333d745e30690c64e83458497b0295ac46361

d4281a22f488970ba086ca475848dedc3db41f77d760a4c280356d1018480ccf

df573b8d4e7ba568670f6fdc9b0078c26ab482ab419a3006e4ed3afc2af946a4

6a83bfd6dc650d7f12e51e39f4a291698962abd8ecdce0840d6786bf0a1e4174

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

Campaign

RLMA-2025-036772025-06-robloxextraRLUA-2026-00725

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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