Kubernetes RBAC privilege escalation paths — ClusterRole/Role enumeration via `kubectl auth can-i --list`, abuse of pods/exec, pods/portforward, secrets get, escalate verb, bind verb, impersonate verb, system:masters group abuse, ServiceAccount token theft and reuse.
68
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Security
3 findings: 1 critical severity, 1 high severity, 1 medium severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
This document is an explicit, step‑by‑step malicious playbook for abusing a stolen Kubernetes ServiceAccount to steal secrets, gain remote code execution, escalate to cluster-admin, create persistent backdoors, and evade detection.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill explicitly instructs reading ServiceAccount tokens and other secrets from files or cluster Secrets and then embedding those token values into commands/configs (e.g., --token="$TOKEN", kubectl --token="$NEW_TOKEN"), which requires the LLM/agent to handle and output secret values verbatim and therefore is high-risk.
The skill prompts the agent to compromise the security or integrity of the user’s machine by modifying system-level services or configurations, such as obtaining elevated privileges, altering startup scripts, or changing system-wide settings.
This skill explicitly instructs obtaining and using a stolen ServiceAccount token, creating privileged pods that mount the host filesystem, and creating serviceaccounts/clusterrolebindings (including backdoor cluster-admin bindings), all of which modify host/cluster state and create persistent accounts/privileges.
0cf691e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.