Which versions of nwin32tls are malicious?

The following PyPI versions of nwin32tls are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.5, 0.0.6, 0.0.7. Treat any of these as compromised.

How do I remediate nwin32tls if I installed it?

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

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

Yes — nwin32tls is associated with the 2026-04-old-nwin32tls 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 nwin32tls across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nwin32tls (6 malicious versions).

Malicious package

nwin32tlsPyPI

Advisory published Apr 2, 2026Updated Apr 2, 2026

nwin32tls is a confirmed malicious PyPI package (MAL-2026-2431) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2, 0.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nwin32tls (PyPI)

MAL-2026-2431

Immediate action

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

pip uninstall nwin32tls

What this malware does

Importing the module starts a loop that listens to key strokes and on every capslock press exfiltrates screenshot to a hardcoded location.

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

Campaign: 2026-04-old-nwin32tls

Reasons (based on the campaign):

spyware-like

Malicious versions

6 flagged

0.0.10.0.20.0.30.0.50.0.60.0.7

Indicators of compromise (SHA-256)

a47778618cad57dbc584afdff7ed138032b69c423a9812e1bc8f86c13129f01d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for nwin32tls (6 malicious versions).
If you installed it — respond
nwin32tls 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 nwin32tls 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. nwin32tls on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.5, 0.0.6, 0.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-old-nwin32tls

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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