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-docker-registryLinux, cloud and containers

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 installs+3 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-docker-registry

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

SignatureSigned, ed25519
a4GdwFe8V7…e5mI6rBQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package2c7a75e8…2d92eed5
2c7a75e876ee…60f62d92eed51 file · ⁦1.4 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/cloud/cloud-docker-registry@ee0e0c5

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

  1. Detect & enumerate: curl -s https://registry:5000/v2/_catalog (repo list) and .../v2/<repo>/tags/list. registry:2 banner / an unauth /v2/ = exposed.
  2. Pull images: docker pull registry:5000/<repo>:<tag> or crane pull (no docker daemon). Anonymous pull of private images is the finding.
  3. Mine layers for secrets: crane export/docker save then scan with trufflehog filesystem / grep for keys, .env, kubeconfig, cloud creds (→ validate with code-review-secrets-detection).
  4. Push (critical): if anonymous/weak push works, you can poison images (supply-chain) — prove with a harmless tag, don't tamper real images.
  5. 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.

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. 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, 2026ee0e0c52c7a75e8Signed–

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