cloud-docker-registry
Find and loot exposed container registries — image pull/push, secrets baked in layers, and registry misconfig. Load on exposed Docker registry (port 5000, /v2/), a registry URL, harbor/ECR/ GCR/ACR references, or "container registry". Signals: /v2/_catalog, registry:2, unauth pull/push.
v2026.10.14-ee0e0c53 installazioni+3 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-docker-registryScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto2c7a75e8…2d92eed5
2c7a75e876ee…60f62d92eed51 file · 1.4 KBScansioneBasso1 segnalazione
- Link a domini esterni
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/cloud/cloud-docker-registry@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When it applies
A Docker/OCI registry is reachable — a self-hosted registry (:5000, /v2/), or a cloud one
(ECR/GCR/ACR/Harbor) with weak auth. Images are goldmines: source, configs, and baked-in secrets.
Why it works
Registries are often deployed without auth ("internal only") or with over-broad pull access. Image
layers preserve everything added at build time — .env files, cloud keys, private source,
tokens — even if a later layer deletes them, earlier layers keep them.
Method
- Detect & enumerate:
curl -s https://registry:5000/v2/_catalog(repo list) and.../v2/<repo>/tags/list.registry:2banner / an unauth/v2/= exposed. - Pull images:
docker pull registry:5000/<repo>:<tag>orcrane pull(no docker daemon). Anonymous pull of private images is the finding. - Mine layers for secrets:
crane export/docker savethen scan withtrufflehog filesystem/ grep for keys,.env, kubeconfig, cloud creds (→ validate withcode-review-secrets-detection). - Push (critical): if anonymous/weak push works, you can poison images (supply-chain) — prove with a harmless tag, don't tamper real images.
- Cloud registries: test misconfigured ECR/GCR/ACR policies; leaked registry creds → pull private images.
Gotchas
- Scan all layers/history, not just the final image — secrets hide in intermediate layers.
- Anonymous push is critical (supply-chain); anonymous pull of private images is high — rate accordingly.
- Only pull what proves the issue; images can be large and contain real data — handle carefully.
Verify success
Anonymous/unauthorized pull of a private image, a live secret extracted from its layers, or a successful (harmless) push proving write access.
References
Docker registry API docs; crane/trufflehog; "hacking Docker registries" write-ups.
File di questa versione
- SKILL.md2.4 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- InfoLink · Link a domini esterni
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 | 2c7a75e8 | 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
- cloud-gcpnoorqureshi/cloud-gcp4
- 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
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