Which versions of rbx1325382 are malicious?

The following PyPI versions of rbx1325382 are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate rbx1325382 if I installed it?

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

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

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

Malicious package

rbx1325382PyPI

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

MAL-2025-41735

Immediate action

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

pip uninstall rbx1325382

What this malware does

During installation, package attempts to exfiltrate browser data

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

Campaign: 2025-07-rbx1325

Reasons (based on the campaign):

infostealer
exfiltration-browser-data

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

ccbf93161f0f4dff5b9e73f44dc977ef1bf3feb81f55cbd30e3903e6624c376c

55588111733b3002535b471510477fe45b31bae56c5abc22d6cf6e755b2cedb6

966cc45844a609edfa292523c993aa173d39c710d8856c06f30d5d73d82f48e9

d77811c6108162fcd8070fbdfae4a80763f9117242574060b9d43fd32928c4c8

7bd5fec19d5b89645e9be1f16d9d6e027a6db91fec4251e8a73f2fd00676abf8

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

Campaign

RLMA-2025-042302025-07-rbx1325RLUA-2026-00689

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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