Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malware in ctx

GHSA-4g82-3jcr-q52w

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI ctx

    Affected
    <= 0.1.4
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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 AWSACCESSKEYID and AWSSECRETACCESSKEY), we advise you to rotate your passwords and keys, then perform an audit to determine if they were exploited.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-4g82-3jcr-q52w

  2. Revision 1 · created ·

    Published from osv record GHSA-4g82-3jcr-q52w

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-4g82-3jcr-q52w

Advisory: Malware in ctx
IDs: GHSA-4g82-3jcr-q52w
Record: https://patchnext.com/advisories/ghsa-4g82-3jcr-q52w (revision 2, source checked 26 Oct 2026, 13:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI ctx: affected <= 0.1.4

## Suggested inspection (read-only)
- `python -m pip show ctx`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ctx.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4g82-3jcr-q52w (OSV record GHSA-4g82-3jcr-q52w lists affected ranges: PyPI ctx >=0 <=0.1.4)
- Verified: https://github.com/advisories/GHSA-4g82-3jcr-q52w (GitHub-reviewed advisory GHSA-4g82-3jcr-q52w lists affected ranges: PyPI ctx >=0 <=0.1.4)

Commands are suggestions: review each one before running it.

Loading voting…