rrsPyPI
Advisory published Updated
rrs is a confirmed malicious PyPI package (MAL-2026-16346) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.3, 0.1.4…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in rrs (PyPI)
What this malware does
On launch of the rrs CLI, a background thread captures a full-screen screenshot via mss and POSTs the image together with hostname, username, OS/release, local IP, and timestamp to a hardcoded Discord webhook at https://discord.com/api/webhooks/1549807268294303860/... The upload runs unconditionally at startup, with no consent prompt and no user-configurable destination; the webhook is controlled by the package author and is not disclosed as a destination for screen contents. Separately, Network.start opens an MQTT connection to the public broker broker.hivemq.com:1883 and publishes a JSON identity record (id, hostname, username, os) to the shared topic rrs/v1/presence every 5 seconds, exposing installer host and user identifiers to any subscriber of that world-readable topic. Screen contents typically include private data, credentials, tokens, and messages visible on the desktop at the moment of capture.
The package automatically and silently exfiltrates screenshots to a hardcoded location.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-09-rrs
Reasons (based on the campaign):
-
spyware-like
-
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for rrs (20 malicious versions).
If you installed it — respond
rrs 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 rrs 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks rrs-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.