Which versions of cscc-glass-house are malicious?

The following PyPI versions of cscc-glass-house are flagged malicious: 1.0.1, 1.0.2, 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate cscc-glass-house if I installed it?

cscc-glass-house 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 cscc-glass-house — how do I know if it already compromised me?

If cscc-glass-house was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is cscc-glass-house part of a known attack campaign?

Yes — cscc-glass-house is associated with the 2026-05-cscc-glass-house 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 cscc-glass-house across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cscc-glass-house (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cscc-glass-house across your stack and pipelines.

Malicious package

cscc-glass-housePyPI

Malicious code in cscc-glass-house (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5096

Immediate action

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

pip uninstall cscc-glass-house

What this malware does

Package implements exfiltrating credentials from cloud environments to a hardcoded location. Some code parts suggest it may be part of a CTF.

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

Campaign: 2026-05-cscc-glass-house

Reasons (based on the campaign):

exfiltration-credentials
exfiltration-env-variables
exfiltration-cloud-tokens

Malicious versions

4 flagged

1.0.11.0.21.0.31.0.4

Indicators of compromise (SHA-256)

20f53888d08d0aa70146b50e8dc761373490363f9081ea0adb9fb93cfd2b6240

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cscc-glass-house (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cscc-glass-house across your stack and pipelines.
If you installed it — respond
cscc-glass-house 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 cscc-glass-house was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks cscc-glass-house before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. cscc-glass-house on PyPI has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-05-cscc-glass-house

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks cscc-glass-house-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