Which versions of woowoowo are malicious?

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

How do I remediate woowoowo if I installed it?

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

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

Yes — woowoowo is associated with the RLMA-2025-04822, 2025-08-k7eel, RLUA-2026-00934 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 woowoowo 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 woowoowo (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 woowoowo across your stack and pipelines.

Malicious package

woowoowoPyPI

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

MAL-2025-47812

Immediate action

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

pip uninstall woowoowo

What this malware does

Importing the module downloads and executes widely recognized malware

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

Campaign: 2025-08-k7eel

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

cf32bd08425b38b3c020fe1d1c6455ff4deb8133aed454672550053bab59ec54

fe636f09ef4bc2cbd8396a8c3038896728b867d91d36802e2e3d8da8fd0228b6

68c093297f2648c1f7fbdccd35b7191bf273b78dbcefdae24c26a9739cfad086

28b972fa3b1e97013a93d57170410da45e3fd0e8a4dc1429cab3891f53c804f9

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 woowoowo (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 woowoowo across your stack and pipelines.
If you installed it — respond
woowoowo 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 woowoowo 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 woowoowo 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. woowoowo 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-048222025-08-k7eelRLUA-2026-00934

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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