loading
Loading content
loading
Cloud Storage
Converts S3 bucket references in many formats into one consistent format for bug bounty and testing.
overview
s3reverse takes a messy list of S3 bucket references and rewrites them into one consistent shape. Bucket names show up across recon output as bare names, path-style URLs, and virtual-hosted-style hostnames, and that inconsistency breaks deduplication and downstream tooling. s3reverse normalizes the list so the next stage works from a single, predictable format.
You feed it an input list and pick the target format: a plain name, an s3 URL, path style like s3.amazonaws.com/bucket, or virtual-hosted style like bucket.s3.amazonaws.com. Output can be normal lines or an array, and an optional verify step checks bucket access while normalizing.
On Trickest, s3reverse is a Cloud Storage node that takes a list of bucket references and writes a file and a folder. Run it between bucket discovery and a scanner so every candidate arrives in the format the scanner expects.
source github.com/hahwul/s3reverse
use cases
Convert a list that mixes names, path-style URLs, and virtual-hosted hostnames into one format so duplicates collapse and downstream tools parse cleanly.
Emit bucket names or s3 URLs in the exact shape a scanner like s3scanner expects, so the discovery-to-scan handoff is clean.
Enable -verify to check bucket access as the list is normalized, flagging which references resolve.
Choose -tP or -tV output to match the addressing convention the rest of the pipeline relies on.
reference
| Name | Type | Flag | Description |
|---|---|---|---|
| input-list | FILE | -iL | Input list of bucket references. |
| to-name-format | BOOLEAN | -tN | Convert to name format (example: github-cloud). |
| convert-to-s3-url | BOOLEAN | -tS | Convert to s3 URL. |
| convert-to-path-style | BOOLEAN | -tP | Convert to path style (example: https://s3.amazonaws.com/github-cloud). |
| convert-to-virtual-hosted-style | BOOLEAN | -tV | Convert to virtual-hosted style (example: github-cloud.s3.amazonaws.com). |
| verify-bucket-access | BOOLEAN | -verify | Verify bucket access. |
| output-format-normal | BOOLEAN | -oN | Write output in normal format. |
| output-format-array | BOOLEAN | -oA | Write output in array format. |
Showing key inputs. s3reverse exposes 8 inputs in total.
example
# normalize mixed bucket refs to bare namess3reverse -iL buckets.txt -tN -oNexample-assetsexample-logsexample-backupsexample-staticexample-uploadsexample-cdnexample-terraform-stateexample-ci-artifactsguidance
Reach for s3reverse when you have a list of S3 bucket references in mixed formats and need them in one consistent shape before scanning. It does not scan or dump buckets itself, so pair it with s3scanner. For finding buckets in the first place, use cloud_enum.
Finds open S3 buckets and dumps their contents, the scanner s3reverse feeds.
Enumerates cloud storage across AWS, Azure, and GCP to discover candidate buckets.
Brute-forces S3 bucket names from permutations to surface new candidates.
faq
A mixed bucket list feeds s3reverse, which normalizes every reference into one format and hands it to s3scanner before results land as a queryable output.
Facts on this page come from the live Trickest tool library.