supply chain event / NVI-00008822 / Revision 1
Malicious code in semverr (PyPI)
GitHub lists this malware advisory for semverr. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
semverr
source listed= 1.0.0
## Source: amazon-inspector (110e0a64dd80654ca98caa5e291499d158a39eb66c1d35efe896a42095c85118) semverr is a near-empty package (a one-line __version__) whose name resembles the popular semver library. Its setup.py runs at install time (invoked by pip during `pip install`) and calls urllib.request.urlretrieve to fetch an opaque binary from https://c2-worker.crawlnet-claim.workers.dev/dl/pyupd, writes it to a PID-suffixed path in the system temp directory, and launches it via subprocess.Popen with start_new_session=True and stdout/stderr redirected to DEVNULL so the detached child survives the install and runs silently. The fetch is unpinned, unverified (no hash or signature check), and directed at an anonymous Cloudflare Workers host unrelated to any declared publisher. Exceptions in the fetch/exec path are swallowed so install still appears to succeed. The package has no other functionality. --- Credit: OpenSSF (source)
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-j4xr-hh3p-8vmm ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.