Which versions of unrartest are malicious?

The following PyPI versions of unrartest are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate unrartest if I installed it?

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

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

Yes — unrartest is associated with the RLMA-2024-09459, 2024-08-koalabuilder, RLUA-2026-00872 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 unrartest 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 unrartest (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging unrartest across your stack and pipelines.

Malicious package

unrartestPyPI

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

MAL-2024-10181

Immediate action

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

pip uninstall unrartest

What this malware does

Packages downloads remote executable. The final behaviour is unknown, but starts with bypassing UAC and other security controls. Some package clones are obfuscated.

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

Campaign: 2024-08-koalabuilder

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5881c13fc435a770a2fd8ed9a39e3a3c88c2d2fd9bee8d31a36006e5c32bb2e2

4fd62d001d9817649e944ffd69f1042efd1d544f7dc38dc59c69258076d8263b

21a41269d4461bf4c85f40299bad3d27a57b45d762da1301cd872bff282c255e

5d2d8c2f0d05e8b20a2cf3ad3af8d82f6188d214a8720aed3afc6192d32ee009

75b3cfd231390181f6d3f1c4039f234c4b7e486433eca940aa35d9de26229d34

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

Campaign

RLMA-2024-094592024-08-koalabuilderRLUA-2026-00872

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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