Which versions of rbx1325 are malicious?

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

How do I remediate rbx1325 if I installed it?

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

If rbx1325 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is rbx1325 part of a known attack campaign?

Yes — rbx1325 is associated with the RLMA-2025-04229, 2025-07-rbx1325, RLUA-2026-00688 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 rbx1325 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rbx1325 (version 0.1.0).

Malicious package

rbx1325PyPI

Advisory published Jul 18, 2025Updated Mar 19, 2026

rbx1325 is a confirmed malicious PyPI package (MAL-2025-41734) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rbx1325 (PyPI)

MAL-2025-41734

Immediate action

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

pip uninstall rbx1325

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)

bebe5dee3157ccb6a495d4d05e497bac97a003eacb695176f14e5a4a0234f044

13681017d263eab485a0645af37533752ade33fbf178268e5d0db204b9891fb5

7895e3c185d37126abdb72411a2b02b7d78325ca51e4cecd4303e282608b8966

8ea5380ef3608fd1dc30aae353de53e9478e90b4b5d454c177a5b175ae0cde89

f68819e4bb4fc0991b2bb865f74961b5eeb856ef43fc83a9a75591eb3b073a9a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for rbx1325 (version 0.1.0).
If you installed it — respond
rbx1325 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 rbx1325 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. rbx1325 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-042292025-07-rbx1325RLUA-2026-00688

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database