cloudbrute
open-sourceThe section your link pointed to isn't on cloudbrute's page any more, so we've brought you to the top.
CloudBrute is a tool to find a company's infrastructure, files, and apps on top cloud providers including Amazon, Google, Microsoft, DigitalOcean, Alibaba, Vultr, and Linode.
Summary
CloudBrute is an open-source command-line tool that hunts for a target company's infrastructure, files, and apps across major cloud providers, including Amazon, Google, Microsoft, DigitalOcean, Alibaba, Vultr, and Linode. It works unauthenticated, generating keyword and environment-based URL mutations to brute-force storage buckets and apps concurrently, with proxy and user-agent randomization to dodge rate limits and region restrictions. You configure it through a YAML file listing providers and environments, then run it as a downloaded binary on Windows, Linux, or Mac. It is built for bug bounty hunters, red teamers, and penetration testers doing black-box recon rather than authenticated cloud audits. First committed in 2020 and now at five contributors and six tracked releases, the project has seen no commits in the past year, so treat it as stable but effectively unmaintained.
CloudBrute is a tool to find a company's infrastructure, files, and apps on top cloud providers including Amazon, Google, Microsoft, DigitalOcean, Alibaba, Vultr, and Linode.
How cloudbrute helps
Which cloud storage buckets has a target company left exposed across the major providers?
generates keyword and environment-based name mutations from the company name and checks them against Amazon, Google, Microsoft, DigitalOcean, Alibaba, Vultr, and Linode storage naming patterns, reporting which guessed bucket names resolve and respond
Which apps or services has a target quietly deployed on Amazon, Google, or Microsoft cloud infrastructure?
runs the same mutation logic against app-hosting URL patterns on those three providers and reports which generated hostnames answer
Can this scan be run against a target without needing any credentials or API access to their cloud accounts?
operates entirely black-box, guessing and requesting URLs unauthenticated rather than querying provider APIs, so it never needs the target's or your own cloud keys
Will hammering a target's cloud assets from one IP with one client signature get the scan rate-limited or blocked by region?
rotates proxies (HTTP or Socks5) and randomizes the user-agent on each request to spread the traffic and avoid triggering rate limits or regional blocks
Which cloud provider actually hosts a given asset once it's found?
cross-checks the discovered host against IPINFO data and the app's source code to identify the underlying provider rather than relying on the URL pattern alone
How do I aim the same hunt at a different company or set of environment names without changing how the tool works?
takes the provider list and environment keywords from a YAML config file, so the mutation wordlist changes per target without touching the binary itself
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for cloudbrute, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail cloudbrute puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
Nothing shipped since we started watching. Releases and docs updates land here as they happen.
Project health
Issue, contributor and maintainer activity in 0xsha/cloudbrute, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 −1 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog 0 of 7 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 0
- Commits / month 0
- Stars 1,148
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →