# pymem-win - compromised PyPI versions

> pymem-win on PyPI has 5 versions flagged in 1 tracked supply-chain incident. Only the exact versions listed below were named by the source advisories. pymem-win was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.

- Package: pymem-win
- Ecosystem: PyPI
- Highest severity: high
- Kind: Advisory sweep
- Compromised versions: 1.14.6, 1.14.5, 1.14.4, 1.14.1, 1.14.0
- Check what you have installed: `pip show pymem-win`

## The incident that flagged it

| Date | Severity | Kind | Incident | Versions named |
|---|---|---|---|---|
| 2026-09-12 | high | Advisory sweep | [GitHub Advisory malware sweep - 2026-09-11/12 (`greensaver` jsonkeeper AES continuation, `tailwind-form-kit` EtherHiding continuation, `2026-09-openaii` AI SDK typosquat wave `langgrap`/`openaii`/`transfomers`/`ollamaa`, `eth-account`/`web3-eth-account` blockchain-C2 pair, `@nimbusedge/auth` dep-confusion reverse shell)](https://dependencywatch.io/incident/multi-2026-09-12-ghsa-malware-sweep) | 1.14.0, 1.14.1, 1.14.4, 1.14.5, 1.14.6 |

## What to do if you installed one of these

1. Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.
2. Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a *different* machine.
3. Pin to a version not listed above, then reinstall from a clean lockfile.
4. Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
5. Read the incident write-up linked above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

## Check your whole project

A compromised package is often a transitive dependency rather than one you installed directly. Paste your requirements.txt to check every dependency at once: https://dependencywatch.io/check/requirements-txt

All flagged PyPI packages: https://dependencywatch.io/package/pypi

## Other packages in the same incident

If pymem-win is in your tree, these are worth checking too - they were published by the same campaign.

- [@nimbusedge/auth](https://dependencywatch.io/package/npm/@nimbusedge/auth) (npm)
- [aitextkit-py](https://dependencywatch.io/package/pypi/aitextkit-py) (PyPI)
- [aitextutils-py](https://dependencywatch.io/package/pypi/aitextutils-py) (PyPI)
- [cr-bot-common](https://dependencywatch.io/package/npm/cr-bot-common) (npm)
- [eth-account-web3](https://dependencywatch.io/package/pypi/eth-account-web3) (PyPI)
- [greensaver](https://dependencywatch.io/package/npm/greensaver) (npm)
- [langgrap](https://dependencywatch.io/package/pypi/langgrap) (PyPI)
- [ollamaa](https://dependencywatch.io/package/pypi/ollamaa) (PyPI)
- [openaii](https://dependencywatch.io/package/pypi/openaii) (PyPI)
- [platform-telemetry-client](https://dependencywatch.io/package/pypi/platform-telemetry-client) (PyPI)
- [strapi-plugin-vinsoc-1109](https://dependencywatch.io/package/npm/strapi-plugin-vinsoc-1109) (npm)
- [tailwind-form-kit](https://dependencywatch.io/package/npm/tailwind-form-kit) (npm)

Full incident: https://dependencywatch.io/incident/multi-2026-09-12-ghsa-malware-sweep

## Sourcing

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Corrections: https://dependencywatch.io/submit

---

Canonical page: https://dependencywatch.io/package/pypi/pymem-win
Markdown version: https://dependencywatch.io/package/pypi/pymem-win.md
Site index for agents: https://dependencywatch.io/llms.txt
DependencyWatch.io is operated by Precursor Security (https://precursorsecurity.com).