Which versions of dmclc are malicious?

The following PyPI versions of dmclc are flagged malicious: 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.5, 2.1.6, 2.1.7, 2.1.9, 2.1.10. Treat any of these as compromised.

How do I remediate dmclc if I installed it?

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

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

Yes — dmclc is associated with the 2026-02-urllib-slim 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 dmclc 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 dmclc (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dmclc across your stack and pipelines.

Malicious package

dmclcPyPI

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

MAL-2026-2106

Immediate action

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

pip uninstall dmclc

What this malware does

During installation, the package starts obfuscated code that downloads and runs remote executables in specific environments - in older packages - attempts to exfiltrate some basic information using DNS requests and then likely cover tracks by installing a similarly named package from private repository

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

Campaign: 2026-02-urllib-slim

Reasons (based on the campaign):

typosquatting
Downloads and executes a remote executable.
obfuscation
dependency-confusion

Malicious versions

9 flagged

2.1.02.1.12.1.22.1.32.1.52.1.62.1.72.1.92.1.10

Indicators of compromise (SHA-256)

895439e6afba407fb85d315e2c99f0d1434905a1ee72b172e62d55abbb8c93a3

29d8ca432d1f2069462955be4a4ea77b5f7c8ee81ec568291be5b0ffce0aeebb

98824533b2b8d26131cde65c6fee280bde414c4810f83d56b6b5f59fc7131df5

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 dmclc (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dmclc across your stack and pipelines.
If you installed it — respond
dmclc 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 dmclc 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 dmclc 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. dmclc on PyPI has been identified as a malicious package (versions 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.5, 2.1.6, 2.1.7, 2.1.9, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-02-urllib-slim

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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