Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/cloud-azureLinux, cloud and containers

cloud-azure

⁨Attack Azure / Entra ID — managed-identity token theft, Entra (Azure AD) role abuse, and app/ storage misconfig. Load when the target is on Azure, you hold Azure creds/a token, or see Entra/AAD/azurewebsites/blob.core.windows.net. Signals: 169.254.169.254 IMDS, Managed Identity, az cli, Entra roles,⁩

v2026.10.14-ee0e0c52 installs+2 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/cloud-azure

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
fzcJy/AjWF…zMW01WDw==The CLI checks the SHA-256 and the signature before it writes a file.
Package8376972e…ada3e113
8376972e7908…b366ada3e1131 file · ⁦1.5 KB⁩
ScanMedium2 findings
  • Link to a raw IP addressSKILL.md:32
  • Links to outside domains
See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/cloud/cloud-azure@ee0e0c5

When it applies

Target on Azure and you have some access — SSRF into a VM/App Service with a Managed Identity, a leaked service-principal secret/cert, or a foothold. Goal: steal tokens, abuse Entra roles, reach resources.

Why it works

Azure resources authenticate via Managed Identities and service principals; the IMDS hands out OAuth tokens for them. Entra (Azure AD) roles and app permissions are widely over-assigned, and several (adding credentials to a service principal, role assignment, Owner on a subscription) escalate to control.

Method

  1. Managed Identity → token (via SSRF, or on the host): GET http://169.254.169.254/metadata/identity/ oauth2/token?api-version=2018-02-01&resource=https://management.azure.com/ with header Metadata: true (→ cloud-imds-ssrf). Also request tokens for Graph, Key Vault, Storage.
  2. Authenticate & enumerate: az login with the SP or token; enumerate roles/resources; map Entra with AzureHound (BloodHound for Azure); ScoutSuite/MicroBurst for misconfig.
  3. Entra / IAM privesc: add credentials to a service principal you can manage → auth as it; abusive Entra roles (Application/Cloud App Admin, Privileged Role Admin); role assignment (Microsoft.Authorization/roleAssignments/write) → grant yourself Owner; consent grants.
  4. Resources & secrets: Key Vault (token for vault.azure.net), Storage blobs (→ storage misconfig), Automation Accounts / runbooks (RCE as their identity), App Service.
  5. Prove impact read-only as the escalated principal; avoid persistent role changes.

Gotchas

  • Two planes: ARM (resources) and Microsoft Graph / Entra (identity) — get tokens for the right resource/audience.
  • Managed-identity SSRF needs the Metadata: true header — header-less SSRF won't work (that's the mitigation).
  • AzureHound reveals Entra attack paths you'd miss manually — run it early.

Verify success

Escalated access proven — a token/role letting you act beyond your start (Key Vault secret read, subscription role you granted, resource action as a managed identity).

References

Azure IMDS & Managed Identity docs; AzureHound/BloodHound; MicroBurst; Entra privesc research.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumLink · Link to a raw IP addressSKILL.md:32
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c58376972eSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login