Which versions of dsodelib are malicious?

The following PyPI versions of dsodelib are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate dsodelib if I installed it?

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

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

Yes — dsodelib is associated with the RLMA-2025-04159, 2025-08-dsidelib, RLUA-2026-00285 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 dsodelib 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 dsodelib (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dsodelib across your stack and pipelines.

Malicious package

dsodelibPyPI

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

MAL-2025-41667

Immediate action

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

pip uninstall dsodelib

What this malware does

Package is runs an Infostealer targeting telegram and Discord credentials. Depending on version, the infostealer is either downloaded from an URL or embedded in the package

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

Campaign: 2025-08-dsidelib

Reasons (based on the campaign):

infostealer
Downloads and executes a remote malicious script.
exfiltration-browser-data
target:telegram

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

6b27710688625d2ed15e6938c7b02f16eb32889d561d3df42b9e1cf0e028c5f9

337f51985af86ea5dd8c09c2b68c3e00de2ec5fb2bed214186690b41aac6f60b

b3646fafa7dac849bdfcdc6c760d037132c5231f61a87721b2a433992a3d3639

aa9a11e54568e85bb542ed0d2532c054eec9bea35998bfb112a3f7688c5d66b7

b5520149f77fc0222db00c867c71c795a618edbc0479610efcdff9cfb07375df

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

Campaign

RLMA-2025-041592025-08-dsidelibRLUA-2026-00285

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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