cloud-iam-deep
Skill7 starsChanged 3 months agoLicence not identifiedView on GitHub
Cloud IAM red-team attack chain across AWS, Azure, GCP — focused on EXTERNAL exploitation paths and post-credential-discovery privilege analysis. Covers IAM enumeration (aws iam, az role, gcloud iam), STS/AssumeRole chaining, Azure Managed Identity abuse (via SSRF/leak), GCP service account JSON abuse, IMDSv1/v2 attacks via SSRF, K8s ServiceAccount token privilege analysis once held (token discovery / cluster exposure is owned by hunt-k8s), role-trust-policy confused-deputy, cross-account assume-role enumeration, IAM privilege escalation patterns (24+ AWS, 8+ Azure, 6+ GCP), and AWS Cognito Identity Pool unauthenticated-role attack chain (GetId → GetCredentialsForIdentity → IAM role abuse). Built for the case where recon yields a credential (key, JSON, token) and you need to know what it grants and how to escalate. Use when an AWS key / Azure secret / GCP service account JSON / K8s SA token surfaces from a code repo, JS bundle, APK, breach corpus, or SSRF chain.
- Reads credentials
- Sends data out
3 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- ajtazer/heckitedited, first seen Sep 11, 2026
- elementalsouls/Claude-BugHunteredited, first seen Jul 1, 2026
- hhjkjkjk/Claude-skillsedited, first seen May 29, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- elementalsouls/Claude-BugHunter★ 6.1k99% same
- ajtazer/heckit★ 299% same
- hhjkjkjk/Claude-skills★ 099% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository98 other files it gives its agents.
- apk-redteam-pipelineSkill
- bb-aiSkill
- bb-apiSkill
- bb-authzSkill
- bb-cloudSkill
- bb-handoffSkill
- bb-injectionSkill
- bb-local-toolkitSkill
- bb-logicSkill
- bb-methodologySkill
- bb-reconSkill
- bb-reportSkill
- bb-verifySkill
- bb-webSkill
- bug-bountySkill
- bugcrowd-reportingSkill
- cv-pentesterSkill
- enterprise-vpn-attackSkill
- evidence-hygieneSkill
- hunt-api-misconfigSkill
- hunt-aspnetSkill
- hunt-atoSkill
- hunt-auth-bypassSkill
- hunt-brute-forceSkill
- hunt-business-logicSkill
- hunt-cache-poisonSkill
- hunt-captcha-bypassSkill
- hunt-cicdSkill
- hunt-clickjackingSkill
- hunt-cloud-misconfigSkill
- hunt-corsSkill
- hunt-csrfSkill
- hunt-deserializationSkill
- hunt-dispatchSkill
- hunt-domSkill
- hunt-exceptional-conditionsSkill
- hunt-file-uploadSkill
- hunt-forgot-passwordSkill
- hunt-graphqlSkill
- hunt-grpcSkill
- hunt-host-headerSkill
- hunt-html-injectionSkill
- hunt-http-smugglingSkill
- hunt-idorSkill
- hunt-jwt-cryptoSkill
- hunt-k8sSkill
- hunt-laravelSkill
- hunt-ldapSkill
- hunt-lfiSkill
- hunt-llm-aiSkill
- hunt-mfa-bypassSkill
- hunt-miscSkill
- hunt-nextjsSkill
- hunt-nodejsSkill
- hunt-nosqliSkill
- hunt-ntlm-infoSkill
- hunt-oauthSkill
- hunt-open-redirectSkill
- hunt-race-conditionSkill
- hunt-rag-vectorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 3 are common, 1 is distinctive, and 1 is very specific to this project.
3
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.