What is VirtuProbe?
VirtuProbe Studio is a multi-protocol integration testing and security assessment tool. It lets you chain interactions across protocol boundaries in a single automated workflow — send an HTTP request, catch the confirmation email over IMAP, extract a token, and use it in an LDAP bind, all in sequence.
Use cases
Section titled “Use cases”Integration testing
Section titled “Integration testing”Validate that systems communicate correctly end-to-end. A typical workflow spans multiple services and protocols — an API call that triggers an email, a token extraction, a directory lookup. VirtuProbe handles the entire chain in one place.
Penetration testing
Section titled “Penetration testing”VirtuProbe implements all protocols from scratch against the RFC specifications — deliberately bypassing standard library constraints. This means you can send malformed packets, craft edge-case inputs, and test boundary conditions that well-behaved clients would never produce. The built-in MITM proxy gives you full visibility and control over raw traffic at the transport layer.
Mail infrastructure testing
Section titled “Mail infrastructure testing”Test the full email pipeline end-to-end: SMTP delivery, spam score evaluation via SpamAssassin, and IMAP retrieval in a single chain.
Supported protocols
Section titled “Supported protocols”| Protocol | Use case |
|---|---|
| HTTP | REST APIs, webhooks, web services |
| SMTP | Mail delivery, command sequence testing |
| IMAP | Mailbox interaction, message retrieval |
| LDAP | Directory lookups, bind auth, entry manipulation |
| SpamAssassin | Spam score evaluation |
Key concepts
Section titled “Key concepts”Probes
Section titled “Probes”A probe is a single protocol interaction saved under a project. You configure the target host, the commands or request to send, and optional assertions. Probes can be sent standalone or used as steps inside a chain.
Chains
Section titled “Chains”A chain is an ordered sequence of probe steps. The output of one step can be extracted into a variable and injected into subsequent steps via {{variable}} placeholders.
Environments
Section titled “Environments”Environments are named sets of key-value variables scoped to a project. Switching the active environment changes the values injected into all probes and chains without modifying the probe configuration itself.
The built-in MITM proxy sits between your client and the target server, capturing raw traffic. A DevTools-style UI lets you inspect request/response pairs with body decompression (gzip, deflate, Brotli).
Architecture
Section titled “Architecture”VirtuProbe runs as two servers:
- UI server — serves the web frontend
- API server — executes probes and manages data
In the desktop app (Electron), both servers start automatically. In a corporate or red-team deployment, the API server can run inside the target network with only a single port exposed to the UI server — the browser never communicates directly with tested systems.