Which versions of sitecard are malicious?

The following PyPI versions of sitecard are flagged malicious: 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. Treat any of these as compromised.

How do I remediate sitecard if I installed it?

sitecard is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed sitecard — how do I know if it already compromised me?

If sitecard was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is sitecard part of a known attack campaign?

Yes — sitecard is associated with the 2026-10-sitecard campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find sitecard across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sitecard (13 malicious versions).

Malicious package

sitecardPyPI

Advisory published Oct 23, 2026Updated Oct 23, 2026

sitecard is a confirmed malicious PyPI package (MAL-2026-18242) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sitecard (PyPI)

MAL-2026-18242

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall sitecard

What this malware does

The package provides code to create an SSH session exposed via tunnels. By default, created session is accessible without any auth and reported to a hardcoded location, exposing any user to be accessed by attacker.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-10-sitecard

Reasons (based on the campaign):

backdoor

Malicious versions

13 flagged

0.1.00.1.10.1.20.1.30.1.60.1.70.1.80.1.90.1.100.1.110.1.120.1.130.1.14

Indicators of compromise (SHA-256)

49be8995374d0e3d2bcb8f163675221e14bfb6d7d968a6fa5d8165e4f493997d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for sitecard (13 malicious versions).
If you installed it — respond
sitecard is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If sitecard was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. sitecard on PyPI has been identified as a malicious package (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, and 5 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-10-sitecard

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks sitecard-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database