OpenBullet 2 is a cross-platform automation suite that allows users to perform web requests, data parsing, and automated penetration testing . One of its most powerful features is the Plugin system
Restart the OpenBullet 2 instance to load the new blocks into the Config Editor. 3. Creating Your Own Plugins Openbullet 2 Plugins
Most config making requires sending requests. You can access OB2's internal HTTP client via the Browser property within the block, but it is often better to inject IRuriLibFunctions. OpenBullet 2 is a cross-platform automation suite that
One of the most famous for bypassing WAF (Web Application Firewall) rules. It rotates user-agents, TLS fingerprints, and even TCP window sizes to mimic real browsers. : Implement custom UI elements, such as dropdown
: Implement custom UI elements, such as dropdown menus with data loaded from external JSON files, to make configs more interactive. Developing a Custom Plugin To start developing, you can use the OB2PluginSample template on GitHub, which provides a well-commented starting point. Key Development Steps: Environment Setup : Install the .NET 8 SDK Project Creation : Create a new class library project or fork the Sample Plugin repository Defining Blocks BlockDescriptor
| Risk | Mitigation |
|------|-------------|
| Malicious plugins accessing filesystem | Run OpenBullet 2 in a sandbox / restricted user account |
| Infinite loops or resource exhaustion | Implement CancellationToken and timeout logic in blocks |
| Dependency conflicts | Use isolated AssemblyLoadContext per plugin (planned for OB2 v2.5+) |
| Sensitive data exposure | Avoid hardcoding secrets; use PluginConfig or environment variables |