Which versions of openrea are malicious?

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

How do I remediate openrea if I installed it?

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

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

Yes — openrea is associated with the RLMA-2024-08611, funcaptcha-ru 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 openrea across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for openrea (version 1.0.0).

Part of a larger attack: funcaptcha-ru published 161 malicious packages. See the full campaign →

Malicious package

openreaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

openrea is a confirmed malicious PyPI package (MAL-2024-10069) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in openrea (PyPI)

MAL-2024-10069

Immediate action

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

pip uninstall openrea

What this malware does

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

Campaign: funcaptcha-ru

Reasons (based on the campaign):

infostealer

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a773396d55e7ec9b16d0c2b887c80f6f06cf3fc07ec4dd446a38b72bf42d3ad9

c21e944e177388736f96590beb4989bf0c097dc11e482186b06e662e6b6267f6

feed5259de4613688d3df61d379566403b7a9e8981937c3b450a7cdc8a99e101

66298c81b843f10b8116fa72ea3515d3e41168765f0c63a6edf5b2dd71ee7f7c

Detection & response playbook

Credential / info stealer

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

Campaign

RLMA-2024-08611funcaptcha-ru

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database