Postman is an awesome platform to build and use APIs, used by millions developers.
It proposes also public API assets built by them which can contains custom endpoints and data. Unfortunately, these items can leak sensitive data about private websites and companies.
This script is aimed to search for these pieces of information in Postman public library.
pip3 install postleaks
or
pip3 install .
❯ postleaks -h
usage: postleaks [-h] [-k KEYWORD] [-kf KEYWORD_FILE] [--extend-workspaces] [--strict] [--include INCLUDE] [--exclude EXCLUDE] [--raw] [--output OUTPUT]
Postleaks 🚀💧 Search for sensitive data in Postman public library.
options:
-h, --help show this help message and exit
-k KEYWORD Keyword (Domain, company, etc.)
-kf KEYWORD_FILE File containing keywords (one per line)
--extend-workspaces Extend search to Postman workspaces linked to found requests (warning: request consuming and risk of false positive)
--strict Only include results where keywords are in the URL (warning: could miss some results where the final URL is a variable)
--include INCLUDE URL should match this string
--exclude EXCLUDE URL should not match this string
--raw Display raw filtered results as JSON
--output OUTPUT Store JSON in specific output folder (Default: results_<TIMESTAMP>)
The results are available in results_<TIMESTAMP>
subfolder. The filename is the request identifier in Postman.com
Postman.com is limiting the results to 300 items (page size of 100 / offset of 200).
Secret detection is done with whispers. Rules are stored in config.yml
file.