Which versions of rwoka are malicious?

The following PyPI versions of rwoka are flagged malicious: 0.1.1, 0.1.2, 0.1.3. Treat any of these as compromised.

How do I remediate rwoka if I installed it?

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

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

Yes — rwoka is associated with the 2024-12-httpfluent 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 rwoka 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 rwoka (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rwoka across your stack and pipelines.

Malicious package

rwokaPyPI

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

MAL-2024-12342

Immediate action

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

pip uninstall rwoka

What this malware does

The package contains highly obfuscated content, that install another, downloaded from a remote location obfuscated script in the installation path of the 'requests' package, and marks it as a hidden system file. In addition, another file contains a code that imitates doing some meaningful activity.

Later attempts hide the malicious code in a separated package, downloaded from Test PyPI.

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

Campaign: 2024-12-httpfluent

Reasons (based on the campaign):

obfuscation
modify-system-without-consent
Downloads and executes a remote malicious script.

Malicious versions

3 flagged

0.1.10.1.20.1.3

Indicators of compromise (SHA-256)

7848d176993ece925fde5b0a5fabfd5511f416a1941f8c2bd2c75294eb580f45

601385385b682f6bdaa31c763e64c5fafb16f22df60acd266c9c7f23f73208ee

843efd20c1b1eb683b623e20818f259ac384a5689493227a5494c7d835bd5ac2

1dc38041bce0bcdea328d90f891e1530a2f7fffd3177884eb4394dad8b4b311d

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

Campaign

2024-12-httpfluent

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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