Skip to content
Projects

Proviesec/directory-files-payload-lists

View on GitHub

Proviesec/directory-files-payload-lists has 90 GitHub stars and 23 forks. GitHot measured 0 stars in 24 hours, +1 in 7 days, and +1 in 15 days. Last checked 2026-11-16 00:50 UTC. Last push 2026-10-25.

How these counts are measured

Measured star growth

in 24h
0
in 7 days
+1
in 15 days
+1
in 1 month
Collecting history

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

About

Directory scans

Security

README.md

Original

Directory and file path wordlists

Path candidates for directory and file discovery during authorized web security work. A matching response is a lead to review, not proof of a vulnerability. Lists contain historical entries and have not been tested against every current product or scanner.

Start here

  1. Pick a list from the catalog. The 20-entry sensitive shortlist is a small starting point; Proviesec's favorites and small-fast-list.txt are broader. The full list is a large historical archive.
  2. Check that the host and paths are in scope. Start with a low request rate and follow the owner's or bug bounty program's rules.
  3. Review responses manually. Many sites return the same page or a redirect for nonexistent paths; status code alone does not establish that a file exists or is exposed. Do not publish sensitive response bodies, credentials, or live target URLs in issues or pull requests.

For example, ffuf accepts a one-path-per-line list. Replace the reserved example hostname with a host you are authorized to assess:

ffuf -w directory-best-sensitive-list.txt -u https://your-authorized-host.example/FUZZ -rate 2 -t 1

PSFuzz is another compatible scanner; check its current command-line documentation before use. The lists themselves make no HTTP requests.

Choosing and interpreting lists

The catalog links every text file and describes its role. File names are retained for existing links, even where the name is historical: top-1000-filenames.txt currently contains 10,202 entries, and small-fast-list.txt contains 4,849. These names do not imply a measured ranking or scan time. The full archive contains 189,477 entries and can be noisy or expensive to run.

Most path lists contain one candidate per line. Some entries begin with /, end with /, contain percent encoding, or include placeholders such as %EXT% in the admin list. Review and adapt them for your scanner and target; do not assume every line is a ready-to-use URL. The phpinfo list also contains legacy expression payloads, so it is not a pure path list.

The file in payload-response/ has a different format: path | possible response text | .... It is a reference for manual response review, not a one-path-per-line scanner input. A text marker by itself is not evidence of a security issue.

Contribute

See CONTRIBUTING.md. Explain why a path belongs in a list, when it is useful, and common false positives. Do not add real secrets, private data, or target-specific URLs. The offline list check catches basic formatting errors, duplicates, and missing entries in the larger lists; it does not validate live results. The mixed phpinfo list remains a formatting exception. The full archive is checked for format and inclusion, but its usefulness has not been validated entry by entry.

License and attribution

The wordlists (*.txt) and documentation (*.md) are licensed under Creative Commons Attribution 4.0 International where copyright or database rights apply. When sharing licensed material, credit Proviesec, link to this repository and the license, and indicate changes. The license does not create rights over unprotected facts or individual common path names. Contributions must be material the contributor is allowed to share under this license.

The Python checker and GitHub Actions workflow are separately licensed under MIT.