Which versions of openwsaa are malicious?

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

How do I remediate openwsaa if I installed it?

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

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

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

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

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

Malicious package

openwsaaPyPI

Advisory published Jun 28, 2024Updated Dec 12, 2025

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

MAL-2024-10088

Immediate action

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

pip uninstall openwsaa

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)

12ced0ad3fa58729e1025ee6bcdc6ec81ae31142e611a20862a5a72f3e07e6c4

013dc21a19e667878a1702d4bf397c09fcdfd7bbb45cc2bd774f78d97c06f33a

7fab4b6cf69d7c696ddad690fd74df945da947a4d854be7e58e30f871cd6edb0

cbec132112d30adb41a4d55e0f4209c968c7953d02dc00bbece5386ab94a93ae

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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