Malicious code in sitecard (PyPI)
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.
Affected packages
PyPI sitecard
- Affected
- >= 0.1.0, <= 0.1.0>= 0.1.1, <= 0.1.1>= 0.1.2, <= 0.1.2>= 0.1.3, <= 0.1.3>= 0.1.6, <= 0.1.6>= 0.1.7, <= 0.1.7>= 0.1.8, <= 0.1.8>= 0.1.9, <= 0.1.9>= 0.1.10, <= 0.1.10>= 0.1.11, <= 0.1.11>= 0.1.12, <= 0.1.12>= 0.1.13, <= 0.1.13>= 0.1.14, <= 0.1.14
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18242 lists affected ranges: PyPI sitecard >=0.1.0 =0.1.1 =0.1.2 =0.1.3 =0.1.6 =0.1.7 =0.1.8 =0.1.9 =0.1.10 =0.1.11 =0.1.12 =0.1.13 =0.1.14 <=0.1.14
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
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.
--- _-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (d9f44333ae4aa62e60d153dfbdc535cd08f778e917a1052ecaf43722d8a7165d) sitecard exposes a workspace directory over SSH via public relays (srv.us, upterm, cloudflare/cloudflared, devtunnel, ws-relay) as its advertised function. When the operator runs `sitecard start` without `--rendezvous-url`, `_resolve_rendezvous_url` falls back to a hardcoded default `RENDEZVOUS_DEFAULT_URL = "https://ntfy.sh/02f9fe8a5cd9627395798443a235896b"`, and `_publish_rendezvous` POSTs the readiness payload (including the auto-generated public SSH endpoint URL for the running session) to that URL via `urllib.request.urlopen`. ntfy.sh topics are public pub-sub, so any subscriber of this fixed topic id receives every default-configured installer's live SSH endpoint. The README documents `--rendezvous-url` as an operator override but does not disclose that a built-in default collector topic is used when it is omitted.…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from osv record MAL-2026-18242
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: mal-2026-18242 Advisory: Malicious code in sitecard (PyPI) IDs: mal-2026-18242 Record: https://patchnext.com/advisories/mal-2026-18242 (revision 1, source checked 30 Oct 2026, 06:25 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 sitecard: affected >= 0.1.0, <= 0.1.0; >= 0.1.1, <= 0.1.1; >= 0.1.2, <= 0.1.2; >= 0.1.3, <= 0.1.3; >= 0.1.6, <= 0.1.6; >= 0.1.7, <= 0.1.7; >= 0.1.8, <= 0.1.8; >= 0.1.9, <= 0.1.9; >= 0.1.10, <= 0.1.10; >= 0.1.11, <= 0.1.11; >= 0.1.12, <= 0.1.12; >= 0.1.13, <= 0.1.13; >= 0.1.14, <= 0.1.14 ## Suggested inspection (read-only) - `python -m pip show sitecard`: 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 sitecard. - 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/MAL-2026-18242 (OSV record MAL-2026-18242 lists affected ranges: PyPI sitecard >=0.1.0 =0.1.1 =0.1.2 =0.1.3 =0.1.6 =0.1.7 =0.1.8 =0.1.9 =0.1.10 =0.1.11 =0.1.12 =0.1.13 =0.1.14 <=0.1.14) Commands are suggestions: review each one before running it.
Loading voting…