OpenBullet 2 plugins provide a clean, extensible architecture for security testers and automation engineers to add custom functionality. While the current implementation has some limitations (no UI extensions, assembly conflicts), the system is robust enough for creating custom blocks, LoliScript functions, and external integrations. Developers should follow security best practices and test plugins in isolated environments before production use.
Disclaimer: This write-up is for educational purposes. Use OpenBullet 2 only on systems you own or have explicit permission to test.
OpenBullet 2 (OB2) uses a hot-loadable plugin system that allows developers to extend the software's functionality without modifying the core source code. These plugins primarily add custom blocks
to the stacker, which can then be used in configurations to handle specialized tasks like advanced encryption, anti-bot bypasses, or integration with external services. 🛠️ Core Purpose of Plugins
Plugins bridge the gap between the standard OB2 toolset and unique site requirements. Custom Encryption
: Implement proprietary algorithms (e.g., HMAC, custom JS WebTokens) to sign requests. Anti-Bot Bypasses Openbullet 2 Plugins
: Add blocks that specifically target advanced detection systems like Cloudflare or Akamai. Captcha Integration
: Connect to specialized third-party solving services not included by default. External Data Handling
: Integrate with databases or proprietary APIs for live data logging or retrieval. Proxy-Seller How Plugins Work in OB2 OB2 is built on
(formerly .NET Core), making its plugin system cross-platform. docs.openbullet.dev Description Hot-Loading
Plugins can be added or removed while the application is running. User-Defined Blocks Disclaimer: This write-up is for educational purposes
Developers write C# code that appears as a new "Block" in the visual editor. File Format Compiled as files and placed in the UserData/Plugins directory. Config Inclusion
When a config uses a plugin-provided block, the plugin's name is noted in the config's JSON metadata. 📂 How to Install and Use Plugins : Obtain the compiled file from a trusted source (e.g., the official OB2 GitHub or verified community forums). : Move the (and any required dependencies) into the UserData/Plugins folder of your OB2 installation. Restart/Scan
: Restart the application or use the "Rescan" feature in the Plugins tab to load the new modules. Implementation : The new blocks will appear in the
under the specific category defined by the plugin developer. docs.openbullet.dev ⚠️ Security and Ethics Risk of Malware : Plugins are executable code. Never run
files from untrusted sources, as they can steal your data or infect your system. While the plugin ecosystem changes frequently (as developers
: While OB2 is a legitimate web testing tool, it is frequently misused for illegal activities like credential stuffing
. Always ensure you have explicit permission to test any target.
If you are looking to build your own, would you like to see a C# code template for a basic plugin or a guide on how to one in Visual Studio? External Libraries - OpenBullet 2
While the plugin ecosystem changes frequently (as developers come and go), several categories and specific plugins have become industry standards.
PLUGIN "DiscordWebhook" "send" "username:password - VALID"
An OB2 Plugin is a compiled .NET library (DLL) written in C#. It allows users to create custom "Blocks" that appear in the OB2 workflow stack.
You can create plugins for:
Most popular plugin type.