Malicious code in roles-royce (PyPI)
-= Per source details. Do not edit below this line.=-
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.
왜 이 VPI인가 (설명가능 · 실험적)
VPI 산정 기준
| 영향도(기본값(정보 없음)) | 55.00 |
| 악용 신호(추가 악용신호 없음) | ×1.00 |
| VPI | 55.00 |
VPI 공식 vpi-v1 기준