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/recon-cloud-assetsLinux, cloud and containers

recon-cloud-assets

⁨Discover an organization's cloud footprint — buckets, blobs, apps, IP ranges, and services across AWS/GCP/Azure. Load during recon on a company target, on "cloud recon", finding storage/assets, or before cloud testing. Signals: an org name/domain in scope, assets on cloud CDNs, wildcard program.⁩

v2026.10.14-ee0e0c52 installs+2 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/recon-cloud-assets

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

SignatureSigned, ed25519
tgJRx4I4gN…ShJXRlBw==The CLI checks the SHA-256 and the signature before it writes a file.
Package2a39a639…c683e412
2a39a6397479…f6ecc683e4121 file · ⁦1.3 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/recon/recon-cloud-assets@ee0e0c5

When it applies

Recon on an org where a lot of surface lives in the cloud. Mapping the cloud footprint surfaces storage exposure, forgotten apps, and IP ranges that feed the cloud-specific skills.

Why it works

Cloud resources use predictable naming and public namespaces (S3 bucket names are global; app services use *.azurewebsites.net, *.appspot.com, etc.). Permuting the org name across providers reveals assets that aren't linked from the main site.

Method

  1. Permutation sweep: cloud_enum -k <company> -k <company>-prod -k <brand> to check AWS S3, Azure blobs/apps, and GCP buckets/apps for names derived from the org.
  2. From existing assets: resolve subdomains/CNAMEs (→ recon-subdomain-enum, recon-dns-analysis) for cloud endpoints (*.s3.amazonaws.com, *.blob.core.windows.net, *.cloudfront.net).
  3. IP ranges / ASN: find the org's ASN and cloud IP ranges; identify origin IPs behind CDNs.
  4. Storage exposure: feed discovered buckets/containers to cloud-s3-exposure (list/read/write test).
  5. Certificate transparency + favicon/Shodan (→ recon-osint) to catch cloud-hosted apps.

Gotchas

  • Stay in scope — cloud recon surfaces third-party SaaS and unrelated tenants; verify ownership.
  • Shared CDNs (Cloudflare/CloudFront) are not the org's infra — don't attack the CDN; find origin.
  • Anonymous bucket testing must be minimal (list/read a marker) — see cloud-s3-exposure for care.

Verify success

A map of in-scope cloud assets (buckets, apps, IP ranges) with any exposed storage flagged for follow-up by the cloud skills.

References

cloud_enum; s3scanner; "cloud recon" methodology; provider public-namespace docs.

Files in this version

Permissions

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

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