Which versions of opensar are malicious?

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

How do I remediate opensar if I installed it?

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

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

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

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

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

Malicious package

opensarPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

opensar is a confirmed malicious PyPI package (MAL-2024-10074) 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 opensar (PyPI)

MAL-2024-10074

Immediate action

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

pip uninstall opensar

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)

57f40b790528c5c5119592a514eef9dd1b842ab2307cff41232ceba40a50b5d2

e6ef8b3042894d4b194147e667c1e4dcf7a0f4647d987a633b908f4ae0dd43a3

a2b194067d7fe54be83a453f0811c940aad8d821a556702f4907bda22d3eb3d1

28131cba4135426fc25267d46b7f137559afb1998e78c0e2bfb6eaa5a345dcf8

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for opensar (version 1.0.0).
If you installed it — respond
opensar 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 opensar 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. opensar 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-08616funcaptcha-ru

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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