Which versions of realstarexx are malicious?

The following PyPI versions of realstarexx are flagged malicious: 1.0.0, 1.0.2. Treat any of these as compromised.

How do I remediate realstarexx if I installed it?

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

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

Yes — realstarexx is associated with the RLMA-2025-05631 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 realstarexx across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for realstarexx (2 malicious versions).

Malicious package

realstarexxPyPI

Advisory published Dec 1, 2025Updated Dec 2, 2025

realstarexx is a confirmed malicious PyPI package (MAL-2025-191656) that executes malicious code on install (malicious versions 1.0.0, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in realstarexx (PyPI)

MAL-2025-191656

Immediate action

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

pip uninstall realstarexx

Malicious versions

2 flagged

1.0.01.0.2

Indicators of compromise (SHA-256)

0cc4c4d72979c8c9f2e12dd2897646249e5cf0bc0c0bcecde134db23809c60b8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for realstarexx (2 malicious versions).
If you installed it — respond
Remove realstarexx 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 realstarexx 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. realstarexx on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05631

Credits

ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database