Plugins — Openbullet 2
If you’re writing your first plugin, start with a simple logging block or a custom proxy source. The API is clean, well-documented in the source code, and surprisingly powerful. Disclaimer: This post is for educational purposes only. OpenBullet 2 should only be used on systems you own or have explicit permission to test. Unauthorized access is illegal.
If you’ve spent any time in the web security testing or automation scene, you’ve likely heard of OpenBullet 2 . It’s a powerful, open-source network testing toolkit that allows security researchers to perform brute-force attacks, credential stuffing simulations, and data parsing. Openbullet 2 Plugins
Out of the box, OpenBullet 2 is impressive. With plugins, it becomes a modular powerhouse. Let’s break down what OpenBullet 2 plugins are, why they matter, and how they extend the core functionality. In version 2 (a complete rewrite of the original OpenBullet in .NET 5+), the developer introduced a proper plugin architecture. Unlike the first version—where you had to manually edit C# scripts or modify the source— OpenBullet 2 plugins are compiled DLLs that you can drop into the Plugins folder. If you’re writing your first plugin, start with
But the real magic?
| Need | Plugin Solution | | :--- | :--- | | Solve a new type of captcha (e.g., hCaptcha with custom payload) | Custom captcha solver plugin | | Generate wordlists on the fly (date-based, pattern-based) | Wordlist generator plugin | | Pull proxies from a Redis list or gRPC endpoint | Custom proxy source plugin | | Add encryption (AES, RSA) inside LoliScript | Custom block plugin | Plugins in OB2 implement specific interfaces from the core OpenBullet2.Core namespace. OpenBullet 2 should only be used on systems