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-urloption, 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
sitecardcommand. 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.13and0.1.14- GitHub lists no patched version. OpenSSF also gives the range
0.*.
Indicators of compromise
- ntfy.sh topic
02f9fe8a5cd9627395798443a235896b src/sitecard/gateway.pysha256a4070098bc39f68bb1f8b2262407c9ec6fee6e30e027cf19ab3761b0a7f0f1c7sitecard-0.1.0-py3-none-any.whlsha256f9dfe626b377efe8eb5d1443b3ffeb0f3b57133e1960e79dfc093779264fc3afsitecard-0.1.0.tar.gzsha256ea79e18cf22cc323e6f726ef7d4d8c0e6eda8e232f4d3ed3cd45c2255468d332
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
- If
pip show sitecardprints a version, stop every running sitecard session. - Run
pip uninstall sitecard. Remove the name from every requirement and lock file. - If a session ran, rotate every password, token and key on that computer. Use a different computer for this.
- 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.