Which versions of roinject are malicious?

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

How do I remediate roinject if I installed it?

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

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

Yes — roinject is associated with the RLMA-2024-09219, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00728 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 roinject 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 roinject (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 roinject across your stack and pipelines.

Malicious package

roinjectPyPI

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

MAL-2024-10158

Immediate action

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

pip uninstall roinject

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)

426bedb2e74a614889b486cbd97376db0265f39b96400b7d4ba5b02e8af64522

ebcebeb148509d0345e7030619ab650d2521222a30e3ab010a51cfe877fbe899

abe077384854dc3572befe16d9f41d68fec2a7dbbc8d38884c526bacf0447318

b6f915859eb0a4b87bc6b8067bf8ccbc3598b35aab079067c313b0d47be13581

616574099147c88cfaf2437a6e541e2ff44eb7e6abf46f80d1a0ed09345d041c

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 roinject (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 roinject across your stack and pipelines.
If you installed it — respond
roinject 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 roinject 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 roinject 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. roinject 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-092192024-08-embeds-RealtekHDAudioManagerRLUA-2026-00728

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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