Which versions of rolib are malicious?

The following PyPI versions of rolib are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate rolib if I installed it?

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

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

Yes — rolib is associated with the RLMA-2024-09220, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00729 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 rolib 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 rolib (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rolib across your stack and pipelines.

Malicious package

rolibPyPI

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

MAL-2024-10159

Immediate action

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

pip uninstall rolib

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a94a70cfc868140513afe105e4e2777ccae797a61f6ffae3086000d34346c7d6

4dc10d22801333d57570e2767150f810c5efa946d75b1322d57dfddf2fec74d0

b16e729f1b088aa209bed8297f772d9b51eccf7c434e2a3b8aa3ff43f17f565e

15c3b800dc65501687aba1fa270e8e188ceb2b36667d6ce93e8a5f478e544288

b87249da1db8ca35d469ecaf25900348d68b5763469c42d204cf2fae92caecf1

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

Campaign

RLMA-2024-092202024-08-embeds-RealtekHDAudioManagerRLUA-2026-00729

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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