Usage Guide

Everything you need to know about running OBM2 Pro, managing proxies, configs, and wordlists.

Before You Start

OBM2 Pro is a web-testing suite intended for authorized security testing, scraping, and automation. Use it only against systems you own or have explicit written permission to test.

⚠

By using this software you agree that you are solely responsible for any actions performed with it. The authors assume no liability for misuse.

Getting Started

Requirements

OBM2 Pro is a portable .NET 10 application: unzip the release folder anywhere and run it — there is no installer. Before the first launch, make sure these runtime components are installed:

ComponentNotes
Windows 10 / 11 (64-bit)Required.
.NET 10 Desktop Runtime (x64)Mandatory — the app will not start without it. Pick the Desktop Runtime, not the SDK or the console runtime.
Visual C++ Redistributable 2015–2022 — x64 + x86Needed by native dependencies (OCR/Tesseract, image processing). The app checks for it on startup and warns if missing.

Automatic updates

From version 4.0.0 onward, OBM2 Pro updates itself. When a newer release is published, the built-in Updater downloads the new package, verifies its integrity (SHA-256), replaces the program files and restarts the app automatically. Your data — configs, wordlists, proxies, settings and hits — is preserved across updates. Releases 3.1.x do not include the updater and must be upgraded to 4.0.0 manually once.

Old configs after updating

Existing configs still load in v4 (the format is backward compatible), but some may need a quick review before use. Several blocks gained new fields in v4, so a value saved for an old field can land in a different field than intended and change the block's behavior.

BlockWhat can happen
Function → RandomStringThe old input can be routed into the new Custom Charset field, so the random string is generated from the wrong character set.
Utility → Convert (and other reworked blocks)New options can shift how the old parameters are interpreted.
⚠

After updating, open, review and re-save any config that uses the changed blocks (RandomString, Utility Convert, etc.). Re-saving rewrites the config with the correct v4 field mapping. Configs that don't use the modified blocks are unaffected.

Main Menu

Launch OB M2 BrowninG.exe. The main menu appears with the following sections accessible from the left navigation rail:

SectionDescription
RunnerExecute configs against wordlists with multiple bots
Proxy ManagerImport, test, and manage proxy lists
Wordlist ManagerRegister wordlist files for use in runners
Config ManagerCreate, edit, and organize LoliScript configs
Hits DBBrowse and export captured hits
ToolsHash, regex, wordlist, domain scanner, and more
SettingsGlobal application settings
OB M2 BrowninG main menu

Runner Manager

The Runner executes a selected config against a wordlist using a configurable number of bots (threads).

SettingDescription
ConfigThe LoliScript config to run
WordlistInput data file (one entry per line)
BotsNumber of concurrent threads
Proxy PoolProxy list to rotate through
SkipNumber of entries to skip from the start
Start / Stop / PauseExecution controls

Bot Statuses

StatusColorMeaning
SUCCESSGreenAll success keychains matched
FAILURERedA failure keychain matched
BANAmberA ban keychain matched (proxy rotated)
RETRYCyanA retry keychain matched (re-queued)
ERRORGrayUnhandled exception during execution
CUSTOMVioletCustom keychain defined in config
Runner Manager

Proxy Manager

Import and manage proxies from files, paste, or an API endpoint. OBM2 Pro supports multiple proxy types:

TypeFormat
HTTP / HTTPShost:port or host:port:user:pass
Socks4host:port
Socks4ahost:port
Socks5host:port or host:port:user:pass
Proxy ChainsMultiple proxies chained for anonymity

Use the Check button to test proxy connectivity. Dead proxies are highlighted in red and can be removed in bulk.

Proxy Manager

Wordlist Manager

Register wordlist files so they appear in the Runner's wordlist picker. Each wordlist has a type that configs can check against.

FieldDescription
NameDisplay name shown in the Runner
PathAbsolute path to the text file
Typee.g. Default, Credentials, Email:Password
PurposeFree-text description

Config Manager

Browse, create, duplicate, and delete LoliScript configs. Configs are stored as .loli or .anom files in the configured configs folder.

Open a config in the Stacker (visual block editor) or the LoliScript editor (text mode). Both views stay in sync.

💡

Use the search bar in Config Manager to filter configs by name. Results update live as you type.

Config Manager

Hits DB

All captured hits (bot status = SUCCESS or CUSTOM with isCapture=true variables) are stored in the built-in LiteDB database.

From Hits DB you can:

  • Filter hits by config name, date range, or custom data
  • Export hits to CSV or plain text
  • Delete individual hits or purge all hits for a config
  • View captured variables per hit

Tools

Built-in utilities accessible from the Tools section:

ToolDescription
HashCompute MD5, SHA1, SHA256, SHA512 hashes
RegexTest regular expressions against sample text
List GeneratorGenerate wordlists from patterns or rules
Wordlist ToolsMerge, deduplicate, split, and convert wordlists
Domain ScannerEnumerate subdomains and DNS records
Convert ToolsBase64, URL encoding, hex conversion
Cookie ConverterConvert browser cookie exports to usable formats
DatabaseRaw LiteDB browser for hits and config data
Selenium ToolsWebDriver management and browser testing
Tesseract DownloadsDownload OCR language data for image captcha solving

Settings

Global application settings are split into tabs:

TabKey Options
GeneralConfigs folder, hits folder, DB path, theme
RunnerDefault bots count, ban keys, retry on ban, proxy rotation
ProxyTLS Proxy port, timeout, connect timeout
CaptchaAPI keys for captcha solving services
SeleniumWebDriver path, default browser, headless mode
RemoteRemote API port and secret key
ℹ

TLS Proxy port must match the port configured in the TLS Request block. Default is 8080. The proxy process (tls-proxy.exe) starts automatically with OBM2 Pro.

Environment Variables

These special variables can be referenced inside configs and affect runner behavior:

VariableDescription
WLTYPEType of the current wordlist (e.g. Credentials). Configs can check this to validate input format.
CUSTOMKCName of a custom keychain to use for this run. Allows dynamic keychain selection.
EXPFORMATExport format for hits. Overrides the default hit format string.