Which versions of pythondm32 are malicious?

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

How do I remediate pythondm32 if I installed it?

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

If pythondm32 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is pythondm32 part of a known attack campaign?

Yes — pythondm32 is associated with the 2025-06-pythondm32 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 pythondm32 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pythondm32 (version 1.1.0).

Malicious package

pythondm32PyPI

Advisory published Jun 21, 2025Updated Dec 12, 2025

pythondm32 is a confirmed malicious PyPI package (MAL-2025-191846) that steals credentials and exfiltrates sensitive data (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pythondm32 (PyPI)

MAL-2025-191846

Immediate action

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

pip uninstall pythondm32

What this malware does

The embedded dm3.1233.dll has a very high recognition as malware

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

Campaign: 2025-06-pythondm32

Reasons (based on the campaign):

malware

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

bf885ef7b93ea634c88824174459583cdba9e3a3cdf0399ff4dc35fdab47b72a

2350dbde660e08d6f97a447886432a41c60802af7e1396dabff53af3ec9091f6

3207664f7e25815a2661e7d0e62269d01fe823637599239dbc1bf335d3343646

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pythondm32 (version 1.1.0).
If you installed it — respond
pythondm32 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 pythondm32 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. pythondm32 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

2025-06-pythondm32

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database