Which versions of nwin64tls are malicious?

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

How do I remediate nwin64tls if I installed it?

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

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

Yes — nwin64tls 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 nwin64tls 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 nwin64tls (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nwin64tls across your stack and pipelines.

Malicious package

nwin64tlsPyPI

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

MAL-2026-2432

Immediate action

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

pip uninstall nwin64tls

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

1 flagged

0.0.1

Indicators of compromise (SHA-256)

72555231efbf126e61cb3aa59d3482bc7967af46898e46eb2b9b7f81af8cd40e

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 nwin64tls (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nwin64tls across your stack and pipelines.
If you installed it — respond
nwin64tls 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 nwin64tls 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 nwin64tls 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. nwin64tls on PyPI has been identified as a malicious package (version 0.0.1 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 nwin64tls-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