spray-dir-brute

Automate directory brute-forcing and fingerprinting of web targets with spray.

1.6k|234|Updated Dec 7, 2019
One-click install
npx skills add https://github.com/wgpsec/AboutSecurity --skill spray-dir-brute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spray-dir-brute
Source: https://github.com/wgpsec/AboutSecurity/tree/main/skills/tool/spray-dir-brute
Command: npx skills add https://github.com/wgpsec/AboutSecurity --skill spray-dir-brute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates high-volume discovery of web directories, backup files, and fingerprints to accelerate web security testing and vulnerability discovery, reducing manual enumeration time.

Core Features & Use Cases

  • High-performance directory brute-forcing with smart filtering to ignore invalid responses.
  • Integrated fingerprinting using multiple libraries to identify CMS/frameworks and technologies.
  • Use Case: Quickly map accessible paths on targets, uncover backup files, and fingerprint technologies for targeted remediation or exploitation planning.

Quick Start

Execute spray against the target using a wordlist to enumerate directories and detect backup files.

Frequently Asked Questions about spray-dir-brute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate directory brute-forcing for multiple web targets?

You can automate directory brute-forcing for multiple web applications by executing spray via command-line with dictionaries, targeting single or multiple URLs to discover accessible directories and backup files.

What is the best way to discover hidden backup files during a web pentest?

The best way to discover backup files during a web pentest is to use spray's high-performance directory brute-forcing with smart filtering, which accelerates enumeration and ignores invalid responses to reveal hidden paths.

How does smart filtering work in web directory scanning?

Smart filtering in web directory scanning works by automatically ignoring invalid HTTP responses during high-volume brute-forcing, ensuring the results returned for directories and backup files are accurate and actionable.

Can I identify CMS and framework fingerprints while brute-forcing directories?

Yes, you can identify CMS and frameworks while brute-forcing directories by applying spray's integrated fingerprinting mode, which uses multiple libraries to detect technologies alongside path enumeration.

Do I need wordlists to perform directory enumeration with spray?

Yes, you need wordlists to perform directory enumeration with spray, as it requires command-line usage of dictionaries alongside optional flags for suffixes, smart filtering, and fingerprinting modes.

What are the limitations of using spray for directory brute-forcing?

Limitations of using spray include its reliance on the quality of provided wordlists and potential performance impacts when scanning multiple high-volume web targets without properly configuring smart filtering.