Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

pymem-winPyPI

pymem-win is a confirmed malicious PyPI package (MAL-2026-16128) that steals credentials and exfiltrates sensitive data (malicious versions 1.14.0, 1.14.1, 1.14.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pymem-win (PyPI)

MAL-2026-16128
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall pymem-win

What this malware does

During import, the obfuscated code downloads and executes an executable. The remote executable did not exist during analysis, but the repository used to host it overlaps with previous campaign 2026-07-yt-api-dlp

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

Campaign: 2026-09-pymem-win

Reasons (based on the campaign):

  • obfuscation

  • Downloads and executes a remote executable.

  • clones-real-package

Malicious versions

5 flagged
1.14.01.14.11.14.41.14.51.14.6

Indicators of compromise (SHA-256)

82eb1f11c9b56a2f2c3e97530db43ef94784a2c75697223828403927b0528477

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pymem-win (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pymem-win across your stack and pipelines.

  2. If you installed it — respond

    pymem-win 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.

  3. Did it already run?

    If pymem-win 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.

  4. How O3 protects you

    O3 blocks pymem-win 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. pymem-win on PyPI has been identified as a malicious package (versions 1.14.0, 1.14.1, 1.14.4, 1.14.5, 1.14.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-pymem-win

References

Credits

  • Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks pymem-win-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore