Which versions of win32con are malicious?

The following PyPI versions of win32con are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate win32con if I installed it?

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

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

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

Malicious package

win32conPyPI

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

MAL-2025-191932

Immediate action

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

pip uninstall win32con

What this malware does

While described as telemetry, importing the package attempts to send out some basic info as well as quite sensitive environmental variables.

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

Campaign: 2025-06-stubsout

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
exfiltration-env-variables

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

a8204b958d08e6a7d5ea23e668e556446f4a774467fac33d71683c2775247db8

b4e7d7a177e3531b4a2566e3c5d1796c1bf18c922bda8943d13e92ef33044141

688e9e96675d223403f45439950adecdd409cf8fa2e9d658735a1b1ffc5a2f4e

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

Campaign

2025-06-stubsout

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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