Which versions of pydeobf are malicious?

The following PyPI versions of pydeobf are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate pydeobf if I installed it?

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

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

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

Malicious package

pydeobfPyPI

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

MAL-2024-11671

Immediate action

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

pip uninstall pydeobf

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.1

Indicators of compromise (SHA-256)

d21600618d4dc4e6de3be78fb8a0692ef975d4abe5769c4de651f3133b9fe48b

56bdf49b67398e6a91171ba152f3ed8d21f0ef5ce38d09668b37146d8ee7d91f

232dd49c6b4b7390c7524bcae8aeee62a5d737258e0cff12a8c7f851a2982ac5

6c94ab57d72954d42c1b5085a575bc7f87510aa3bd706b3b12ffb9bd9c1394af

cf519a5fddf2934861d239d965675d019d973f4681b361cd7fd9674d0b25778b

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

Campaign

RLMA-2024-111282024-08-embeds-RealtekHDAudioManagerRLUA-2026-00626

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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