DependencyWatch.io
Talk to PrecursorScan a lockfile

urc has 1 compromised version.

MediumAdvisory sweepPyPI

urc has 1 version on PyPI flagged in 1 incident we track. Only the exact versions listed below were named by the source advisories. urc 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.

Check my requirements.txtWhat to do
At a glancePyPI
1
Compromised versionDo not install these

If one is in your tree, treat the machine as compromised, not just out of date.

Ecosystem
PyPI
Worst severity
Medium
Incidents
1
First flagged
20 Sept 2026
Type
Advisory sweep

Version data comes from the public advisories cited on each incident page.

Affected versions

The exact releases to look for.

Check what you actually have installed with pip show urc.

  • urc@99.99.99
The incident

The incident that flagged it

MediumAdvisory sweep

GitHub Advisory malware sweep, 20 September 2026

GHSA 2026-09-19 late + 2026-09-20: only one new advisory in the 24h window - pip urc@99.99.99 (GHSA-3c7m-3qhf-wqrr, MAL-2026-16298), a setup.py-override install-time host-info exfiltrator (IP + username) flagged by GHSA as PROBABLY_PENTEST under campaign GENERIC-standard-pypi-install-pentest. Cataloguing depth reserved for the corresponding named incident when a payload appears; no worm / hijack / typosquat cluster in this window.

Versions named here: 99.99.99Read the incident →
What to do

Installed one of these? Start here.

Treat the machine as compromisedUpgrading is not enough. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

  1. Rotate every credential that machine or CI job could reach, such as registry tokens, cloud keys, SSH keys and CI secrets, from a different machine.
  2. Pin to a version not listed above, then reinstall from a clean lockfile.
  3. Clear caches and private mirrors. Artifactory, Nexus, Verdaccio and devpi routinely keep serving a tarball after the public registry has pulled it.
  4. Read the incident write-up. Recommended actions differ per incident, and some have specific indicators of compromise worth searching your logs for.

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name and do not infer additional ones. Think this is wrong or incomplete? Tell us.

Check your whole project

Check every dependency, not just this one.

It is usually pulled in as a transitive dependency rather than one you installed directly. Paste your requirements.txt to check every dependency at once. It runs in your browser and nothing is uploaded.

Check my requirements.txtAll PyPI packages