How severe is GHSA-4g82-3jcr-q52w?

No CVSS score has been assigned to GHSA-4g82-3jcr-q52w yet. Review the advisory details and affected package list to assess your exposure.

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

GHSA-4g82-3jcr-q52w affects the following packages: ctx (PyPI). Ecosystems affected: PyPI.

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

The records we use list no patched version of ctx for GHSA-4g82-3jcr-q52w. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-4g82-3jcr-q52w in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ctx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4g82-3jcr-q52w if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-4g82-3jcr-q52w actively exploited in the wild?

No public exploit code has been indexed for GHSA-4g82-3jcr-q52w yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-4g82-3jcr-q52w published, and has it been updated?

GHSA-4g82-3jcr-q52w was published on May 25, 2022. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

Malware in ctxGHSA-4g82-3jcr-q52w

GHSA-4g82-3jcr-q52w is a security vulnerability in ctx. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published

May 25, 2022

Updated

May 25, 2022

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of May 25, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍ctx

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

The ctx hosted project on PyPI 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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ctx`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ctx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of ctx for GHSA-4g82-3jcr-q52w. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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 `A

O3 Security · Impact-Aware SCA

Is GHSA-4g82-3jcr-q52w in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works