supply chain event / NVI-00008517 / Revision 1
Malicious code in semvver (PyPI)
GitHub lists this malware advisory for semvver. 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.
semvver
source listed= 1.0.0
## Source: amazon-inspector (bbc16b0ced0bad1a33b912dfdb29cbaef211f30974d942991257d4e6b60a8ece) setup.py performs an install-time fetch-and-execute: it calls urllib.request.urlretrieve against https://c2-worker.crawlnet-claim.workers.dev/dl/pyupd, writes the response to a temporary path, and spawns it as a detached background process via subprocess.Popen with start_new_session=True. The fetch is unpinned and has no hash or signature verification, exceptions are swallowed, and the destination is a Cloudflare Workers subdomain unrelated to any PyPI publisher identity. The package has no other functionality — __init__.py is empty and the description is a generic 'utility helpers' string — so the install hook is the package's entire payload. The downloaded binary name 'pyupd' is a cover-story label; the behavior is a classic install-time dropper that grants whoever controls the Workers endpoint arbitrary code execution on the installer's host, running detached and persisting beyond the pip process. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/e29c7e37b0612ba04bf703b601e4f2a2ac4a98de/osv/malicious/pypi/semvv
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-9mgr-73fh-p55h ↗
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.