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-iam-privescLinux, cloud and containers

cloud-iam-privesc

⁨Escalate privileges in cloud IAM (AWS/GCP/Azure) from a low-priv set of credentials. Load when you hold cloud creds/keys/a role and want higher privilege or new resources. Signals: leaked AWS keys, an assumed role, a service-account token, "escalate in AWS/GCP/Azure", enumerated permissions.⁩

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-iam-privesc

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

SignatureSigned, ed25519
X8dYDRRLXK…i7rB4dBQ==The CLI checks the SHA-256 and the signature before it writes a file.
Packageb24b9737…c50e6975
b24b97377999…4dc1c50e69751 file · ⁦1.4 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/cloud/cloud-iam-privesc@ee0e0c5

When it applies

You have some cloud identity (leaked keys, an SSRF-obtained role — cloud-imds-ssrf, a compromised service account) and want to escalate to admin or reach more resources.

Why it works

IAM is complex and permissions are over-granted. A handful of seemingly-minor permissions form known escalation paths — creating a policy version, attaching a policy, passing a role, updating a function's code/role — that promote a low-priv identity to admin.

Method

  1. Identify & enumerate: aws sts get-caller-identity; enumerate your effective permissions (enumerate-iam, pacu, or read attached policies). GCP: gcloud ... get-iam-policy; Azure: az role assignment list.
  2. Find an escalation primitive (AWS examples):
    • iam:CreatePolicyVersion / SetDefaultPolicyVersion → grant yourself *.
    • iam:AttachUserPolicy / PutUserPolicy → attach AdministratorAccess.
    • iam:PassRole + lambda:CreateFunction/ec2:RunInstances/glue/cloudformation → run code as a privileged role.
    • iam:CreateAccessKey on another user; sts:AssumeRole on an over-trusting role. GCP: iam.serviceAccounts.actAs, setIamPolicy, editor→owner via deploymentmanager.
  3. Execute the path (in scope), then confirm elevated access with a read-only admin call.
  4. Automate discovery with pacu (AWS) escalation modules / ScoutSuite for the landscape.

Gotchas

  • Enumerate permissions first — escalation depends entirely on which ones you hold.
  • Prove escalation with a minimal, reversible action; don't create lasting admin backdoors on a live account (RoE).
  • Temp creds expire — capture get-caller-identity before and after as proof.

Verify success

You gain permissions/resources beyond your starting identity (e.g. an admin-only call now succeeds, or you assume a higher-priv role), demonstrated with before/after identity.

References

Rhino Security "AWS IAM privilege escalation" methods; Pacu; GCP/Azure privesc guides; ScoutSuite.

Files in this version

Permissions

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

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

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, 2026ee0e0c5b24b9737Signed–

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