PyPI

The sitecard PyPI Supply Chain Attack

Updated 16 Nov 2026 · Incident date 22 Sept 2026

Every release of sitecard on PyPI, 0.1.0 to 0.1.14, opens SSH access to a work folder with no login by default.

OpenSSF and GitHub list every release of the PyPI package sitecard as malware. PyPI no longer serves the package, so its code was not available for inspection.

What happened

OpenSSF record MAL-2026-18242 and GitHub advisory GHSA-9wjg-8fcv-pxj2 describe the facts below.

  • sitecard exposes a work folder over SSH through public relays.
  • By default, the SSH session needs no login.
  • Without the --rendezvous-url option, the package posts the public SSH address to a fixed ntfy.sh topic.
  • Amazon Inspector states that the session starts only when a person runs the sitecard command. Install and import do not start it.
  • Amazon Inspector and Kamil Mańkowski (kam193) reported it. OpenSSF and GitHub published the records on 23 October 2026.

Version 0.1.0 came out on 22 September 2026. Version 0.1.14 came out on 18 October 2026.

Affected versions

  • 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 and 0.1.14
  • GitHub lists no patched version. OpenSSF also gives the range 0.*.

Indicators of compromise

  • ntfy.sh topic 02f9fe8a5cd9627395798443a235896b
  • src/sitecard/gateway.py sha256 a4070098bc39f68bb1f8b2262407c9ec6fee6e30e027cf19ab3761b0a7f0f1c7
  • sitecard-0.1.0-py3-none-any.whl sha256 f9dfe626b377efe8eb5d1443b3ffeb0f3b57133e1960e79dfc093779264fc3af
  • sitecard-0.1.0.tar.gz sha256 ea79e18cf22cc323e6f726ef7d4d8c0e6eda8e232f4d3ed3cd45c2255468d332

How to check

List the installed version in each Python environment.

pip show sitecard

Search your requirement and lock files for the name.

grep -rn "sitecard" requirements*.txt pyproject.toml poetry.lock uv.lock 2>/dev/null

What to do now

  1. If pip show sitecard prints a version, stop every running sitecard session.
  2. Run pip uninstall sitecard. Remove the name from every requirement and lock file.
  3. If a session ran, rotate every password, token and key on that computer. Use a different computer for this.
  4. Search your proxy and DNS logs for ntfy.sh requests from that computer.

What Vigilance would show

Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.

On the computer, at install

Vigilance blocked `sitecard` 0.1.0. This version is too new or changed in a way Vigilance must check first.

In the owner report

Bad update

sitecard 0.1.0

This update now downloads from the internet and runs other programs. The version before it did not.

Frequently asked questions

Is sitecard safe to use?

No. OpenSSF and GitHub list every release as malware, and no fixed version exists.

Does installing sitecard start the SSH session?

No. Amazon Inspector states that the session starts only when a person runs the sitecard command.

Sources

  1. github.com/advisories/GHSA-9wjg-8fcv-pxj2
  2. osv.dev/vulnerability/MAL-2026-18242
  3. raw.githubusercontent.com/ossf/malicious-packages/main/osv/malicious/pypi/sitecard/MAL-2026-18242.json
  4. libraries.io/pypi/sitecard/versions

More supply chain attacks

All 150 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library