Which versions of ora3 are malicious?

The following PyPI versions of ora3 are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate ora3 if I installed it?

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

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

Yes — ora3 is associated with the RLMA-2025-02583, 2025-04-alchemyrpcs, RLUA-2026-00571 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 ora3 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 ora3 (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ora3 across your stack and pipelines.

Malicious package

ora3PyPI

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

MAL-2025-4227

Immediate action

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

pip uninstall ora3

What this malware does

Package contains just a function to send out data. It (or a package sharing the same IoCs) is used in a malicious GitHub project to exfiltrate crypto currency private keys, e.g. https://github.com/taikoyaki/MegaEth-Auto-Bot/blob/772b4591daaa0b200d1bd1fd3be3d48b8433f084/cap/cap.py#L49

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

Campaign: 2025-04-alchemyrpcs

Reasons (based on the campaign):

crypto-related
The malicious code is intentionally included in a dependency of the package
exfiltration-crypto

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

3e9ccbd45ce93dd3f137ea4f701778a436e728ec6fd949233260028b77ba42be

648e18c09c710ee958148bb49302774de54247db119d64d965e2cf7423e051fc

9d9ff95457d63990b263b77b0f3468dcd63e0d1837c81843b2d4249706db48c7

0efaafa71b57fac1dfe5fbcfbacf5079d8dd0b8bfb2bf00048a8e1e40aa535e7

6690d2e7dae52525202947ad678e8539680a60e0c4bd0a287a132a1bc4eb115a

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

Campaign

RLMA-2025-025832025-04-alchemyrpcsRLUA-2026-00571

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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