Which versions of regixtest are malicious?

The following PyPI versions of regixtest are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4. Treat any of these as compromised.

How do I remediate regixtest if I installed it?

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

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

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

Malicious package

regixtestPyPI

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

MAL-2025-48896

Immediate action

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

pip uninstall regixtest

What this malware does

Obfuscated code contains e.g. capabilities for downloading and executing code from a hardcoded location. It's also recognized as malware

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

Campaign: 2025-10-regixtest

Reasons (based on the campaign):

obfuscation
action-hidden-in-lib-usage
Downloads and executes a remote malicious script.
malware

Malicious versions

5 flagged

0.1.00.1.10.1.20.1.30.1.4

Indicators of compromise (SHA-256)

be8183115c7e3df98800c36287295b44e30a6457baf95f4324af022bbf5d47e4

eb1666d5e5f9c7c5bb2bfbaf1c95f07ad154bfe1596127f62da8b8349107a5db

5bd4402c3382436a949c662f36088697ac7a3a0fd22e2c91fdf2102231e2392c

6f5d3e60ec1b5684e600480df0fd6dee11c8a0d6ed4985ef10705d9154951fb8

4f2344312262cff9d61a447d9fd8f490873d82951334be092c5750463c15e19e

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

Campaign

RLMA-2025-052152025-10-regixtestRLUA-2026-00692

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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