Check out: “OpenBullet: A Black-Box Analysis of a Credential Stuffing Framework”
Published on HackerOne/Hacktivity, 2021
Includes:
Open the wordlist file in a text editor (Notepad++ recommended).
Look at the first 5–10 lines:
The error "OpenBullet this config does not support the provided wordlist type" is frustrating but almost always fixable. It’s not a bug — it’s a safeguard to prevent OpenBullet from feeding garbage data into a config expecting a clean structure.
By understanding the relationship between configs and wordlist types, you can convert, remap, or reconfigure your way to a successful run. Whether you’re a beginner or an experienced user, the solutions above will get your automation back on track.
Remember: Always test with a small wordlist first, read the config’s requirements, and keep your lists well-organized. Happy auditing.
Word Count: ~1,250
Target Keyword: "openbullet this config does not support the provided wordlist type"
SEO Meta Description: Fix the OpenBullet error “this config does not support the provided wordlist type” with 6 working solutions. Convert wordlists, edit configs, and avoid the mismatch permanently.
This error occurs when the Wordlist Type assigned to your imported data file does not match the Allowed Wordlist Types specified within your OpenBullet configuration's settings. Core Causes Mismatched Attributes
: The config is hard-coded to only accept certain types (e.g., Credentials
), but you imported your wordlist as a different type (e.g., Missing Environment Definitions
: If the specific wordlist type name used in the config isn't defined in your Environment.ini file, OpenBullet cannot validate the data correctly. Resolution Steps 1. Adjust Config Settings (Most Common Fix)
You must explicitly tell the configuration which data types it is allowed to process. Config Manager and select the problematic config. Navigate to Config Settings Other Options depending on your version). Locate the Allowed Wordlist Types
Move the wordlist type you are using (e.g., "Credentials" or "EmailPass") from the "Available" side to the the configuration before starting the job. 2. Re-import the Wordlist
When importing a new list, ensure you select the correct category that matches what the config expects. section and click
dropdown, select the category that matches your config's requirement (standard options usually include Credentials 3. Update the Environment.ini
If the required wordlist type is missing entirely from your environment, you must add it manually to the OpenBullet Usage Manual configuration file. Environment.ini Check out: “OpenBullet: A Black-Box Analysis of a
Ensure it contains the definition for the type you need, such as:
[WORDLIST TYPE] Name=Credentials Regex=^.*:.*$ Verify=True Separator=: Slices=USERNAME,PASSWORD Use code with caution. Copied to clipboard Restart OpenBullet after saving changes for them to take effect. Technical Overview Table Wordlist Type Categorizes data lines (e.g., email:pass vs user:pass). Allowed Types
A security/logic gate in the config to prevent using wrong data formats.
Validates that each line in your file matches the expected format. , lines that don't match the regex are marked as INVALID. for a specific data format?
"This config does not support the provided wordlist type" in OpenBullet occurs when the specific data type assigned to your imported wordlist (e.g., Credentials
) is not listed as an "Allowed Wordlist Type" within the configuration settings. Core Cause OpenBullet uses Wordlist Types (WLTYPE) to define how data lines (like
) are validated and split into variables. If a config is strictly built for but you attempt to run it with a wordlist imported as Credentials , OpenBullet will block the job to prevent variable errors. How to Fix the Error Method 1: Update Config Settings (Recommended)
You can tell the configuration to accept your specific wordlist type. OpenBullet and navigate to the Select the config you want to use and go to its Look for the Other Options Allowed Wordlist Types
and add the type that matches your wordlist (e.g., if your wordlist is "EmailPass", ensure "EmailPass" is checked or listed). the config and restart the job. Method 2: Re-import or Edit Wordlist Type
Alternatively, you can change the type assigned to the wordlist itself so it matches what the config expects. : Delete the wordlist from the tab and re-import it, ensuring you select the correct Wordlist Type Credentials ) from the dropdown menu during the import process. Direct Edit : In some versions, you can right-click the wordlist in the Wordlist Manager and select to change its type. Method 3: Modify the Environment.ini If you frequently use custom types (like
), you may need to define them in your environment settings. Locate the Environment.ini file in your OpenBullet root folder. Ensure the [WORDLIST TYPE]
definitions match the syntax and separators your wordlist uses.
Note that the first type listed in this file is often the default for new configs. Common Wordlist Types Expected Format Variables Created Credentials input.USER input.PASS email@domain.com:pass input.EMAIL input.PASS username:pass input.USER input.PASS input.DATA Do you need help defining a custom regex for a new wordlist type in your Environment.ini
[REQUEST] Wordlist with Multiple Types · Issue #590 - GitHub 7 Apr 2020 —
The "This config does not support the provided Wordlist Type" error in OpenBullet occurs when you attempt to run a job using a wordlist that hasn't been enabled in the specific configuration's settings . OpenBullet uses these types (like Credentials, Emails, or UserPass) to determine how to parse each line of your data file into variables like input.USERNAME and input.PASSWORD . Open the wordlist file in a text editor
Below is a blog-style guide to understanding and fixing this mismatch.
How to Fix: "This config does not support the provided Wordlist Type" 1. Update the Config Settings (The Quick Fix)
Most of the time, the configuration simply needs to be told that your wordlist type is acceptable.
Open the Config: Go to the Config Manager and select the config you want to use.
Navigate to Settings: Go to Config Settings > Other Options (or Data in OpenBullet 2) .
Enable the Type: Look for a section labeled Allowed Wordlist Types.
Select Your Type: Check the box for the wordlist type you are trying to use (e.g., if your wordlist is "MailPass," ensure "MailPass" or "Credentials" is selected) .
Save: Don't forget to save the config before restarting your job. 2. Re-Import Your Wordlist
If you accidentally imported your wordlist with the wrong type (e.g., imported a list of emails as Default instead of Credentials), the config will reject it even if the data looks correct. Go to the Wordlist Manager. Delete the current wordlist entry. Click Add and re-select your file .
In the Type dropdown, carefully select the format that matches your data (usually Credentials or UserPass) . 3. Modify the Environment.ini File (Advanced)
If you are using a unique data format that isn't listed, you can define it yourself in the core settings.
Locate the Environment.ini file in your OpenBullet root or UserData folder .
Under the [WORDLIST TYPE] section, you can add a new type with a custom Regex and Slices .
Example: Name=MyCustomList, Regex=^.*:.*$, Separator=:, Slices=USER,PASS . Restart OpenBullet for these changes to take effect . Why does this happen?
OpenBullet is designed to be modular. A config built to check Proxy Lists shouldn't accidentally be run with a list of User:Pass combos. By enforcing "Wordlist Types," the software ensures that the script has the exact variables it needs to function properly . Word Count: ~1,250 Target Keyword : "openbullet this
Do you need help defining a custom regex for a specific wordlist format in your Environment.ini?
[REQUEST] Wordlist with Multiple Types · Issue #590 - GitHub
In the OpenBullet Config editor (specifically inside the Start Block or Key Block), the developer assigns variables to slices of the wordlist line.
For example, if a config is designed for a MailPass wordlist, the developer might write code like:
DATA "email" "password"
This tells the runner: "When you read a line, split it at the colon (:). Call the first part 'email' and the second part 'password'."
If you feed this config a UserPass wordlist (e.g., johndoe:123456), the config might fail if it tries to validate the email format, or it might simply reject the wordlist type entirely if the author has implemented strict type checking (which is what causes this specific error message).
This OpenBullet error means the config (the attack script or module) expects a specific wordlist format/type (e.g., plain usernames, username:password pairs, or JSON) but the wordlist you loaded uses a different format. OpenBullet validates the wordlist type against what the config declares and refuses to run when they don’t match.
If you have the
This error is a common "gatekeeper" in OpenBullet that occurs when the Wordlist Type (e.g., Email:Pass) does not match the Config's Requirement (e.g., Credentials). 🛠️ Why This Error Happens
OpenBullet configs are coded to parse specific formats. If a config is designed to use Credentials (usually User:Pass) but you upload a wordlist set to Emails (Email:Pass), the software blocks the runner to prevent a "parsing error" during the check. 💡 How to Fix It (The Quick Way) Go to the Runner tab. Look at your Wordlist selection. Change the Type dropdown to match what the config expects.
Common swaps: Change "Emails" to "Credentials" or "Default." Re-start the Runner. ⚙️ How to Fix It (The Permanent Way)
If you are the config creator or want to modify it so it always accepts your list type: Go to the Config Manager tab. Select your config and click Edit. Navigate to the Settings tab within the config editor. Go to General. Locate the Allowed Wordlist Types list.
Add the type you are trying to use (e.g., Email:Pass or Credentials). Save the config. 🔍 Understanding Wordlist Types Credentials: Generally used for User:Pass. Emails: Specifically for Example@mail.com:Pass. Numeric: Used for Phone:Pin or ID:Code. URLs: Used for scraping or crawling tasks.
📌 Pro Tip: If you aren't sure what the config needs, check the Stacker or LoliScript tab. Look at how the variables are defined (e.g.,
A relevant academic paper covering similar errors in tooling:
“Understanding and Detecting Credential Stuffing Attacks in the Wild”
Authors: Kurt Thomas et al. (IEEE S&P 2019)
While not explicitly about OpenBullet’s error message, it discusses: