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-s3-exposureLinux, cloud and containers

cloud-s3-exposure

⁨Find and prove misconfigured cloud object storage (S3/GCS/Azure Blob). Load when assets load from *.s3.amazonaws.com, storage.googleapis.com, *.blob.core.windows.net, bucket-looking hostnames, or "bucket". Signals: public-read/list, unauthenticated writes, predictable bucket names.⁩

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-s3-exposure

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

SignatureSigned, ed25519
oRa70Qx9nT…8P7rBoCQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package32d325b5…e02f39e2
32d325b5b2c0…2ce1e02f39e22 files · ⁦2.6 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-s3-exposure@ee0e0c5

When it applies

The app stores files in S3/GCS/Azure Blob and the bucket's ACL/policy is too open — public listing, public read of private objects, or (worst) unauthenticated write.

Why it works

Object-storage ACLs are easy to get wrong: "public" gets applied at the bucket level, or an IAM policy grants s3:ListBucket/GetObject/PutObject to *. Predictable names (companyname-backups, -assets, -dev) make discovery trivial.

Method

  1. Find bucket names: from asset URLs, JS, DNS CNAMEs, and permutations of the org name (company, company-prod, company-backups, region suffixes).
  2. Test list/read (S3): aws s3 ls s3://bucket --no-sign-request (list) and aws s3 cp s3://bucket/file . --no-sign-request (read). --no-sign-request = anonymous.
  3. Test write (high impact, do carefully & in scope): aws s3 cp poc.txt s3://bucket/ --no-sign-request — a successful anonymous write is critical (defacement/malware hosting).
  4. GCS/Azure: gsutil ls gs://bucket / anonymous HTTPS GET; Azure ?comp=list on the container.
  5. Scale carefully with s3scanner/gcpbucketbrute on name lists — respect scope & rate.

Gotchas

  • 403 on the bucket root ≠ safe — individual objects may still be public; test known object paths.
  • Anonymous write is the crown jewel but easy to over-test — upload one harmless marker, then stop.
  • Region matters for the endpoint; a wrong region gives misleading 301/403.

Verify success

Anonymous listing/read of non-public objects, or a successful anonymous write of a harmless proof file (then remove it). Capture the exact command + response.

References

AWS S3 security docs; "hacking the cloud" S3 guides; s3scanner README.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
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, 2026ee0e0c532d325b5Signed–

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