cloud-gcp
Attack Google Cloud Platform — metadata/SA token theft, IAM privilege escalation, and storage/ function misconfig. Load when the target runs on GCP, you hold a GCP SA key/token, or see gcp/gcloud/GCE/GKE/appspot. Signals: metadata.google.internal, service-account.json, storage.googleapis.com, cloudf
v2026.10.14-ee0e0c54 installazioni+4 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/cloud-gcpScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto0f159f8a…af9b86ff
0f159f8a54d9…94acaf9b86ff1 file · 1.5 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/cloud/cloud-gcp@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When it applies
The target is on GCP and you have some access — an SSRF into a GCE/GKE instance, a leaked service account (SA) key, or a foothold in a workload. Goal: steal credentials, escalate IAM, reach data.
Why it works
GCP identity centers on service accounts and IAM bindings that are frequently over-granted. The
metadata server hands SA tokens to anything on the instance, and a small set of permissions
(actAs, setIamPolicy, deploy roles) form known escalation paths to owner.
Method
- Metadata → SA token (via SSRF, or on the host):
GET metadata.google.internal/computeMetadata/v1/ instance/service-accounts/default/tokenwith headerMetadata-Flavor: Google(→cloud-imds-ssrf). Also grab.../scopesand project info. - Authenticate & enumerate:
gcloud auth activate-service-account --key-file=sa.json;gcloud projects get-iam-policy, list what the SA can do; ScoutSuite for the landscape. - IAM privesc paths:
iam.serviceAccounts.actAs+ deploy (Cloud Functions/Run/Compute) to run as a higher-priv SA;iam.serviceAccounts.getAccessToken/signJwt/implicitDelegation;setIamPolicy(editor→owner);deploymentmanagerrunning as the default SA. - Data & services: enumerate GCS buckets (→
cloud-s3-exposureequivalents), Cloud SQL, secrets in Secret Manager, and GKE (→cloud-kubernetes). - Prove impact with a read-only call as the escalated identity; don't create lasting bindings.
Gotchas
- SA scopes (legacy) can restrict a token even with broad IAM — check both scope and IAM.
actAs+ a deploy permission is the classic privesc — hunt for it specifically.- Org policies/VPC-SC may block exfil paths; note them rather than forcing.
Verify success
Escalated access proven — a call succeeding as a higher-priv SA, secret/data read you shouldn't
have, or gcloud acting with permissions beyond your starting identity.
References
GCP IAM docs; Rhino Security GCP privesc research; ScoutSuite; "hacking GCP" guides.
File di questa versione
- SKILL.md2.7 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 0f159f8a | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in Linux, cloud e container
Vai alla categoria- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
- container-image-hardeningsecurityskills/container-image-hardening3
- performing-cloud-incident-containment-proceduresmukul975/performing-cloud-incident-containment-procedures3
- implementing-taxii-server-with-opentaxiimukul975/implementing-taxii-server-with-opentaxii3
- detecting-cryptomining-in-cloudmukul975/detecting-cryptomining-in-cloud3
- detecting-azure-service-principal-abusemukul975/detecting-azure-service-principal-abuse3
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login