Which versions of embeds are malicious?

The following PyPI versions of embeds are flagged malicious: 0.0.1, 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate embeds if I installed it?

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

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

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

Malicious package

embedsPyPI

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

MAL-2024-11581

Immediate action

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

pip uninstall embeds

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

3 flagged

0.0.10.0.20.0.3

Indicators of compromise (SHA-256)

4f197f7c0a21ef5132ea2fad03ded8c0cd05bb2f39fea8dff3d9859a20c47180

49492ba5c8b62deaa22d792804ce7cdecdf24b6fe6337aceaba224e4375c80ed

46ae6a18503196c40e7fd1759d8a68025e6a980a64821c2a1232b7f76fbc2779

e83145521ad7515bd369532c4dc751eba1871bcd29538383876fcb37d9916ec5

c8521676cb05d393199c28933ea94ce60ba460a32b7aa942bd08df0bb11c0128

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

Campaign

RLMA-2024-110312024-08-embeds-RealtekHDAudioManagerRLUA-2026-00293

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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