Check S3 bucket permissions and dump the open ones

S3Scanner takes a list of candidate bucket names and reports which are misconfigured, then optionally pulls down what is inside. Open or world-readable object storage is a recurring source of data exposure, so it turns a raw candidate list into a per-bucket verdict: the permissions each one grants and, with dumping on, the files it leaks.

Scan mode checks bucket permissions without reading the contents; dump mode downloads what an open bucket holds. It reads names from a file with --buckets-file and threads the work so a long list clears quickly, while --endpoint-url and --endpoint-address-style point it at S3-compatible stores beyond AWS.

Reach for S3Scanner once you already hold bucket names, from cloud_enum discovery or s3reverse normalization. It confirms exposure and captures evidence in one pass, then writes a file and a folder you can route to the rest of a workflow.