# GHSA-4g82-3jcr-q52w: Malware in ctx

> A compromised PyPI package exfiltrated environment variables to a remote server, exposing sensitive credentials to attackers.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2022

## What is GHSA-4g82-3jcr-q52w?

GHSA-4g82-3jcr-q52w is a vulnerability in ctx, published on 25 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The `ctx` hosted project on [PyPI](https://pypi.org/project/ctx/) was taken over via user account compromise and replaced with a malicious project which contained runtime code that collected the content of `os.environ.items()` when instantiating `Ctx` objects. The captured environment variables were sent as a base64 encoded query parameter to a heroku application running at `https://anti-theft-web.herokuapp.com`.

If you installed the package between May 14, 2022 and May 24, 2022, and your environment variables contain sensitive data like passwords and API keys (like `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`), we advise you to rotate your passwords and keys, then perform an audit to determine if they were exploited.

## Which versions are affected by GHSA-4g82-3jcr-q52w?

2 open source packages ship an affected version, including ctx.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ctx` | PyPI | All versions to 0.1.4 | None |
| `ctx` | PyPI | All versions to 0.1.4 | None |

## How do I fix GHSA-4g82-3jcr-q52w?

No fix has been published for GHSA-4g82-3jcr-q52w yet. Limit exposure of the affected software until one is available.

## Is GHSA-4g82-3jcr-q52w being exploited?

There is no known exploitation of GHSA-4g82-3jcr-q52w in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4g82-3jcr-q52w and fix it if it is affected.

What it is: GHSA-4g82-3jcr-q52w is a vulnerability in ctx, published on 25 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-4g82-3jcr-q52w in the wild and no public exploit code.

Affected packages and fixed versions:
- ctx (PyPI): affected all versions up to 0.1.4; no fix listed
- ctx (PyPI): affected all versions up to 0.1.4; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-4g82-3jcr-q52w/ (Markdown: https://insights.sbomify.com/GHSA-4g82-3jcr-q52w/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4g82-3jcr-q52w

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4g82-3jcr-q52w/
Summaries are generated and may contain mistakes; the official description above is the record.