go get -u github.com/smiegles/mass3mass3 -w ./lists/buckets.txt -r ./lists/resolvers.txt -t 100| argument | explanation |
|---|---|
| -w | The wordlist with all the pre-compiled S3 buckets (bucketname.s3.amazonaws.com) |
| -r | List with all the resolvers |
| -t | The amount of threads to use, 10 is default |
| -o | The file path to save the output (This is optional. By default, it will be saved to out.csv) |
docker build -t <name> .
docker run -it <name> -w buckets.txt -r resolvers.txt -t 100 -o /tmp/out.csv
Q: Why not generate all the "potential" s3 bucket names in the tool?
A: This tool doesn't know the recon you've already collected, for example, subdomains. When you have a huge list of subdomains you can run alt-dns over it and try to find other S3 buckets that might not have a DNS record configured (yet).
Q: The tool returns weird non-existing buckets
A: The tool relies on the lists/resolvers.txt file to be accurate without any "bad" resolvers. You can use fresh.sh to clean up the list of resolvers.
Q: How many threads should I use?
A: Depends on your resources, I personally use 500 threads which seems to work fine for me.
Credits to @koenrh who created s3enum. I used some parts of his code and the way he identifies if a S3 bucket exists using DNS.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent