Which versions of dlibex are malicious?

The following PyPI versions of dlibex are flagged malicious: 1.11, 1.12. Treat any of these as compromised.

How do I remediate dlibex if I installed it?

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

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

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

Malicious package

dlibexPyPI

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

MAL-2024-11579

Immediate action

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

pip uninstall dlibex

What this malware does

When importing the module and a specific file exists in the current directory, obfuscated code downloads and starts the next stage of obfuscated code (cstealer infostealer)

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

Campaign: 2024-10-pyutiltool

Reasons (based on the campaign):

infostealer
obfuscation
infostealer:cstealer

Malicious versions

2 flagged

1.111.12

Indicators of compromise (SHA-256)

da5b6ebfd0a5dd68ce049c1b23b17538d9dd49ad3f8213592d2a256d302b11a9

354b2659a697b8e1572736c9a422924475846315fe21a4ef9fc7479c4efabee2

334235bba91ccf5f6b15b680b7e549e46b7de4a3007d30337b3e72a5124048b6

badf29842bedf65fa9148f5ec86cdc6b9a087fbaeb4e57f8b7b67a5f91e5b375

b91d21cc79df4f5479c74ff857826cf3163895cd87a2ddcec80e3d5569abd8d3

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

Campaign

RLMA-2024-110292024-10-pyutiltoolRLUA-2026-00278

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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