Which versions of roles-royce are malicious?

The following PyPI versions of roles-royce are flagged malicious: 2.1.0, 2.1.1. Treat any of these as compromised.

How do I remediate roles-royce if I installed it?

roles-royce 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 roles-royce — how do I know if it already compromised me?

If roles-royce 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 roles-royce part of a known attack campaign?

Yes — roles-royce is associated with the IN-MAL-2026-010798, 2026-07-roles-royce, IN-MAL-2026-011043 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 roles-royce across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for roles-royce (2 malicious versions).

Malicious package

roles-roycePyPI

Advisory published Jul 20, 2026Updated Aug 4, 2026

roles-royce is a confirmed malicious PyPI package (MAL-2026-10927) that steals credentials and exfiltrates sensitive data (malicious versions 2.1.0, 2.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in roles-royce (PyPI)

MAL-2026-10927

Immediate action

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

pip uninstall roles-royce

What this malware does

roles_royce/init.py invokes a hidden _check_env() routine at import time that spawns a background thread harvesting installer secrets — SSH private keys under ~/.ssh/id_, ~/.aws/credentials, ~/.config/gcloud/.json, ~/.kube/config, ~/.npmrc, ~/.pypirc, ~/.docker/config.json, ~/.gitconfig, ~/.git-credentials, ~/.gnupg/private-keys-v1.d/, ~/.ethereum/keystore/ wallet keystores, shell histories, and.env* files across Desktop/Projects/repos/code/src/work. The collected files are zipped, base64-encoded, and POSTed together with the full os.environ (truncated per variable) and the Kubernetes service-account token/namespace read from /var/run/secrets/kubernetes.io/serviceaccount/token to two hardcoded IPv4 endpoints (185.158.107.189:8877 and 151.247.22.13:8877). The destinations are stored as integer tuples in a variable named _ANALYTICS and reassembled at runtime by a helper _fa; the module is named _compat.py, the entry function is check(), and staging paths use .compat-/.compat_cache.zip naming to present the routine as a runtime compatibility check. A fallback exception path re-POSTs dict(os.environ) to the same endpoints. The package advertises itself as a Zodiac Roles transaction builder; the exfiltration behavior is unrelated to that purpose.

During import, the package exfiltrates sensitive data (env variables, credential files, shell history, cryptocurrency wallet data etc.). It appears to be targeting users of kpk.io with names the same or similar to the legitimate packages they offer in different ecosystems.

First discovered by Amazon Inspector.

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

Campaign: 2026-07-roles-royce

Reasons (based on the campaign):

dependency-confusion
targetted-attack
exfiltration-credentials
exfiltration-env-variables
exfiltration-cloud-tokens
exfiltration-ssh-keys
exfiltration-crypto

Malicious versions

2 flagged

2.1.02.1.1

Indicators of compromise (SHA-256)

318b93ddaafba751bab93b48efbef99f4eb45f143b019d7ff0f74735e434f378

e4a24ac9bb2fd9263f35109916cd093952633bc0e04714f3986c8627f6a22291

4de67ca22fa0696133924c12b6ab51d0c609dded7ad99176331e4efc05ddd09a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for roles-royce (2 malicious versions).
If you installed it — respond
roles-royce 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 roles-royce 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. roles-royce on PyPI has been identified as a malicious package (versions 2.1.0, 2.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-0107982026-07-roles-royceIN-MAL-2026-011043

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks roles-royce-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