rasterkit-demoPyPI
rasterkit-demo is a confirmed malicious PyPI package (MAL-2026-10975) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in rasterkit-demo (PyPI)
What this malware does
rasterkit-demo ships a CLI entry point (rasterkit-demo) whose run_demo() function imports demo_channel_windows from PIL._data and passes the returned buffer to exec(samples.decode('latin-1'), {'__name__': '__main__',...}) inside worker threads. PIL._data is not a real Pillow module; it is supplied by the rasterkit package that this demo declares as a required dependency, so the bytes being executed are chosen at runtime by the author-controlled rasterkit package rather than by Pillow. The surrounding functions (extract_windows, render_tiles, save_tiles) and the 'channel window / processing pipeline' docstrings provide imaging cover for what is arbitrary Python execution; the payload can be changed at will by publishing a new version of rasterkit without republishing this package. Running the advertised CLI therefore executes attacker-mutable code on the installer's machine under an image-processing cover story.
During import, the code uses steganography to extract code from an image hidden in the dependency. The code then adds a new authorized SSH key and reports back the IP of the current environment.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-06-textwrap-toolkit-stager
Reasons (based on the campaign):
-
backdoor
-
obfuscation
-
crypto-related
-
Downloads and executes a remote malicious script.
-
exfiltration-crypto
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rasterkit-demo (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rasterkit-demo across your stack and pipelines.
If you installed it — respond
rasterkit-demo 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 rasterkit-demo 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 rasterkit-demo 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks rasterkit-demo-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.