Table of contents
What is this?
Where did you get these?
It's worth noting that none of the secrets here are real. They are all things I've seen before, but I've randomized or redacted all of the actual data. The vast majority of secrets will likely be taken from patterns created for github-dorks, which are primarily taken from config files for popular services. I've also worked on several scanning tools in the past. Most notably, github-dorks, PasteHunter, github-dorks, as well as GHScraper, and several other non-public or unreleased scanners. Essentially, I've seen a lot of whoopsies on git, which will also be included.
Why did you make this repo?
This repo was made to serve as a benchmark for secrets scanners. Repo scanning tools have varying levels of coverage, and so far the go-to option has been "slam a bunch together". This repo is also partially to test my theory that this technique still isn't really sufficient. Regardless, you can't just scan for high entropy, and you can't just scan for patterns, you need to do both!
How can I avoid uploading these secrets?
I've written a blog post on Why We Fail at Keeping Git Secrets. If you truly want to keep your secrets safe, seperate them from your repo. If that's a config file, that's fine. If it's a secrets management/storage system, that's even better. As long as you can stop git from adding that information by default, you're unlikely to hit any problems.
|.npmrc||NPM registry authentication data|
|.dockercfg||Docker registry authentication data|
|misc-keys/cert-key.pem||PEM Private key|
|misc-keys/putty-example.ppk||PuTTYgen private key|
|.ssh/id_rsa||Private ssh key|
|.ssh/id_rsa.pub||Public ssh key (might still not be ideal)|
|db/dump.sql||MySQL dump w/ bcrypt hashes|
|cloud/.credentials||S3 Credentials file|
|cloud/.s3cfg||S3 Credentials file|
|cloud/.tugboat||Digital Ocean tugboat config|
|web/var/www/public_html/wp-config.php||WordPress config file|
|web/var/www/public_html/config.php||PHP application config file|
|web/var/www/.env||Laravel .env (CI, various ruby based frameworks too)|
|.git-credentials||Git credentials store|
|.bashrc||.bashrc file (contains several secrets as environment variables)|
|.bash_profile||.bash_profile file (contains several secrets as environment variables)|
|db/robomongo.json||Mongolab credentials for robomongo|
|db/mongoid.yml||Mongoid config file|
|web/js/salesforce.js||Salesforce credentials in a nodejs project|
|.netrc||netrc with SMTP credentials|
|hub||Hub config that stores github tokens|
|filezilla/filezilla.xml||Filezilla config file|
|filezilla/recentservers.xml||Filezilla recent servers file|
|.docker/config.json||Docker registry authentication file|
|db/.pgpass||PostgreSQL file which contains passwords|
|/proftpdpasswd||Usernames and passwords of proftpd created by cpanel|
|etc/shadow||Linux /etc/shadow file|
|db/dbeaver-data-sources.xml||DBeaver config containing MySQL Credentials|
|.mozilla/firefox/logins.json||Firefox saved password collection (can be decrypted using keys4.db)|
|web/django/settings.py||Django setup.py, contains valid secret key|
|web/ruby/secrets.yml||Ruby on rails secrets.yml file (contains passwords)|
|ruby/config/master.key||Rails master key (used for decrypting
|deployment-config.json||Created by sftp-deployment for Atom, contains server details and credentials|
|.ftpconfig||Created by remote-ssh for Atom, contains SFTP/SSH server details and credentials|
|.remote-sync.json||Created by remote-sync for Atom, contains FTP and/or SCP/SFTP/SSH server details and credentials|
|.vscode/sftp.json||Created by vscode-sftp for VSCode, contains SFTP/SSH server details and credentials|
|sftp-config.json||Created by SFTP for Sublime Text, contains FTP/FTPS or SFTP/SSH server details and credentials|
|.idea/WebServers.xml||Created by Jetbrains IDEs, contains webserver credentials with encoded passwords (not encrypted!)|
|high-entropy-misc.txt||Misc high entropy strings (HES1 is plain, HES2 is base64)|
We've tested a few tools and generated metrics for it. You can see how the tools tested so far stack up in Benchmarking
If there's a tool you'd like tested, please file an issue with details on it or create a PR. We are focused primarily on command-line based tools, but are also happy to accept results from web or GUI-based tools, as long as you include the full results and details about the tool.
It's also worth noting that many of the original patterns used to find the filenames and examples of several secrets came from github-dorks, which is under tha Apache 2.0 License. Also, for the sake of full disclosure, I am a maintainer on that project.