Which versions of starexx are malicious?

The following PyPI versions of starexx are flagged malicious: 1.26, 1.27, 2.0.1. Treat any of these as compromised.

How do I remediate starexx if I installed it?

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

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

Yes — starexx is associated with the RLMA-2025-05639, RLUA-2026-00781 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 starexx across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for starexx (3 malicious versions).

Malicious package

starexxPyPI

Advisory published Dec 1, 2025Updated Mar 19, 2026

starexx is a confirmed malicious PyPI package (MAL-2025-191662) that executes malicious code on install (malicious versions 1.26, 1.27, 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in starexx (PyPI)

MAL-2025-191662

Immediate action

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

pip uninstall starexx

Malicious versions

3 flagged

1.261.272.0.1

Indicators of compromise (SHA-256)

68768312d951897277716f45e240107c3873276fcf03efcf72dbcf9ca8ccd67d

9b766367622c8636c39e85c01b0992b44bb599691ea933788debbf1d4f1c5008

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05639RLUA-2026-00781

Credits

ReversingLabs · finder

Detect & block this

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