Azure Managed Identity abuse — IMDS at 169.254.169.254 from compromised VM / App Service / Function, token exchange for Graph/ARM/KeyVault, federated workload identity abuse, hybrid AAD Connect MSOL credential extraction.
67
81%
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 how-to for abusing Azure Managed Identities (stealing IMDS/workload tokens, exfiltrating secrets, pivoting and OPSEC to evade detection), indicating deliberate malicious intent.
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 prompt explicitly instructs retrieving managed identity access tokens and including them verbatim in commands/Authorization headers (curl/powershell), which requires the LLM to handle and output secret token values directly.
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 stealing managed identity tokens, reading local secrets (IMDS and pod projected tokens), and even tells the operator to "Run as SYSTEM" to extract AAD Connect credentials, which directs privilege escalation and exfiltration from the host and therefore compromises machine state.
e34afba
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.