OpenBullet configs are structured automation scripts that orchestrate HTTP requests, data extraction, captcha handling, and response validation. They perform tasks such as sending requests, parsing data, bypassing anti-bot measures, and more.
Configs typically contain metadata such as the config name, author, and input types. This information helps users understand the origin and intended use of the config.
The input setup section in a config specifies the account format (e.g., username:password, email:password), proxy types (HTTP, SOCKS5, residential proxies), and header spoofing methods (e.g., random User-Agent, language, cookies). These setups help mimic real user behavior.
Request blocks are used to send HTTP requests (such as POST, GET, etc.) with parameters, cookies, and headers. Here, users can define the specific method, URL, headers, and body for the request.
For example, a POST request might look like this:
1{
2 "method": "POST",
3 "url": "https://target.com/api/login",
4 "headers": {
5 "User-Agent": "<RANDOM>",
6 "Content-Type": "application/json"
7 },
8 "body": "{\"username\":\"<USER>\",\"password\":\"<PASS>\"}"
9}
10Parse blocks are used to extract data from the response. This can be done through regex, JSONPath, or CSS selectors. For instance, extracting specific content from an HTML response or extracting tokens from a JSON response.
KeyCheck blocks are used to verify if a login attempt was successful based on the response content. This typically involves checking for keywords like "Dashboard" or "Welcome" in the response body.
Here’s a regex example to extract the CSRF token from the response:
1{
2 "type": "regex",
3 "source": "<RESPONSE>",
4 "pattern": "name=\\\"csrf_token\\\" value=\\\"(.*?)\\\"",
5 "capture": "CSRF"
6}
7Configs are not hacking tools; they are logic engines for automation. By understanding their structure and the technologies involved, you can unlock the true potential of automation.