Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
dicozorus — A tool to generate and maintain wordlists for Web fuzzing. | Kitploit
Tools/GitHubGitHub/synacktiv/dicozorus
ReconnaissanceVulnerability AnalysisInformation GatheringWeb SecurityFuzzingPenetration TestingCurated Resources
GitHubsynacktiv/dicozorus

dicozorus

A tool to generate and maintain wordlists for Web fuzzing.

View Repository
15141 month agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Dicozorus

Dicozorus is a tool to generate and maintain web wordlists.

It eliminates the overhead of managing multiple wordlists by storing paths enriched with metadata in a local SQLite database.

Just want a great wordlist without the tool? Skip the setup and use lazy.txt.

Why Dicozorus?

Standard wordlists often present problems such as missing entries, lack of relevant sorting, inappropriate size or junk entries.

Dicozorus solves these issues by associating entries with enriched metadata. This allows:

  • Smart Sorting: Places the most critical and highly probable entries at the top of your list so you find valuable endpoints faster.
  • Targeted Extension Filtering: If a site runs PHP, you can skip ASP and JSP extensions entirely, saving time and network bandwidth.
  • Adaptive Sizing: Easily scale your wordlist size depending on target stability, rate limits, or network connectivity.
  • Contextual Fuzzing: Generate lists specifically tuned for directory fuzzing, file fuzzing, or both.

Installation

root@kitploit:~
$ pipx install git+https://github.com/synacktiv/dicozorus/

Dicozorus overview

dicozorus_overview

Architecture & Data Storage

Dicozorus stores data locally in an SQLite database located at $HOME/.dicozorus/db.sqlite. Each entry tracks the following attributes:

Dicozorus built-in wordlists

For more convenience, dicozorus is packed with built-in wordlists. The entries present in these wordlists comes from various locations:

  • Others wordlists or projects (dirsearch, bo0om, Seclist, nuclei. etc.)
  • Public vulnerability reports (HackerOne reports, ExploitDB vulnerabilities, Github Advisories)
  • Redteam / Pentests feedbacks
dicozorus_sources

Current set of built-in wordlists

lazy.txt

Each time a change is made to the built-in wordlists, lazy.txt is generated. It includes all built-in entries except dangerous ones, sorted by criticality and count.

Usage

root@kitploit:~
$ dicozorus
usage: dicozorus [-h] [-v] [--version] {feed,gen,init,modify,stats,check} ...

Dicozorus allows to generate custom wordlists. It can be fed with wordlists from your own or initialized using a predefined set of wordlists. Entries are
stored in a sqlite database located in $HOME/.dicozorus/db.sqlite

positional arguments:
  {feed,gen,init,modify,stats,check}
                        Subcommand to run
    feed                Feed dicozorus db with wordlist files or scan results
    gen                 Generate wordlist using the dicozorus db.
    init                Initialize the dicozorus database.
    modify              Modify dicozorus DB directly. Use it to add / remove / update one or multiple entries.
    stats               Show stats about the dicozorus database.
    check               The check command is used to compare entry or wordlists with the dicozorus database

options:
  -h, --help            show this help message and exit
  -v, --verbose         increase verbosity
  --version             show program's version number and exit

Initialize the dicozorus database

root@kitploit:~
$ dicozorus init -F -W wordlists/
[+] Initializing dicozorus database
[+] Creating dicozorus tables
[+] Parsing dicozorus CSV file wordlists/low.wordlist
[+] Parsing dicozorus CSV file wordlists/unranked.wordlist
[+] Parsing dicozorus CSV file wordlists/hackerone.wordlist
[+] Parsing dicozorus CSV file wordlists/medium.wordlist
[+] Parsing dicozorus CSV file wordlists/exploitdb.wordlist
[+] Parsing dicozorus CSV file wordlists/critical.wordlist
[+] Parsing dicozorus CSV file wordlists/high.wordlist
[+] Parsing dicozorus CSV file wordlists/bo0om.wordlist
[+] Parsing dicozorus CSV file wordlists/seen.wordlist
[+] Parsing dicozorus CSV file wordlists/info.wordlist
[+] Parsing dicozorus CSV file wordlists/dirsearch.wordlist

Feed the dicozorus database

root@kitploit:~
$ dicozorus feed -w fuzz.txt
[+] Parsing wordlist fuzz.txt

Generate a wordlist

root@kitploit:~
$ dicozorus gen -m 5
app_dev.php
actuator/jolokia
jolokia
bitrix/admin/php_command_line.php
jenkins/script

Check the metadata associated with a specific entry

root@kitploit:~
$ dicozorus check -e '_fragment'
_fragment [type: FILE, criticality: CRITICAL, count: 2, category: RCE, taglist: ['PHP', 'Bo0oM'], reference: https://www.ambionics.io/blog/symfony-secret-fragment]

Show stats about the dicozorus database

root@kitploit:~
$ dicozorus stats
[+] Total count: 22376
[+] Entry count by criticality:
	Critical: 344
	High: 697
	Medium: 668
	Low: 1168
	Info: 4262
	Unranked: 15237
[+] Entry count by type:
	FILE: 12583
	DIRECTORY: 3449
	PATH: 6344
[+] Entry count by category:
	UNCATEGORIZED: 19499
	KNOWN_APP: 871
	RCE: 335
	INFO_LEAK: 280
[...]

Contributing

Custom CSV Format

If you want to contribute entries to the core lists or parse custom inputs natively, use the following quoted Comma-Separated Values (CSV) structure:

root@kitploit:~
## path, criticality, count, category, tags, reference
"actions/authenticate.php","CRITICAL","1","RCE","PHP","https://nvd.nist.gov/vuln/detail/CVE-2020-35729"

Adding an entry to the built-in wordlists

Here are a few rules when adding entries to the built-in wordlists:

  • If the entry is associated with a criticality you can put it in one of the following files in dicozorus/data/ :
    • CRITICAL.wordlist
    • HIGH.wordlist
    • MEDIUM.wordlist
    • LOW.wordlist
  • If the entry is not associated with any criticality, but the entry looks interesting and generic you can put it in the INFO.wordlist file.
    • Examples of generic interesting entries: upload.php, admin.aspx, webshell.jsp, administration/
  • If the entry Criticality is LOW or above, you must add a reference to the CSV file
Download Tool
FieldDescription
pathThe endpoint name (e.g., jmx-console/ or app-dev.php).
typeStructural classification: FILE, DIRECTORY, or PATH.
criticalityPriority tier: CRITICAL, HIGH, MEDIUM, LOW, INFO, UNRANKED.
countHow many times this specific URL has been fed into the database.
categoryType of vulnerability it is attached (e.g., RCE, ADMIN_INTERFACE or KNOWN_APP)
tagContextual tags for technology filtering (e.g., PHP, JAVA, LINUX).
referenceAn optional link to an associated vulnerability, advisory, or known endpoint documentation.
NameDescription
critical.wordlistCRITICAL entries only
high.wordlistHIGH entries only
medium.wordlistMEDIUM entries only
low.wordlistLOW entries only
info.wordlistINFO entries only
unranked.wordlistEntries with no affected criticality
bo0om.wordlistEntries from BoOoM wordlist with no affected criticality
dirsearch.wordlistEntries from dirsearch wordlist with no affected criticality
exploitdb.wordlistEntries from exploitDB with no affected criticality
hackerone.wordlistEntries from HackerOne public reports with no affected criticality
seen.wordlistEntries that were seen here and there, with no affected criticality
dangerous.wordlistDangerous entries such as /shutdown or reboot