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 |
| DNS | Name resolution, record queries, RCODE assertions |
| SpamAssassin | Spam score evaluation |
| SMB | Share enumeration, file operations, NTLM auth, pass-the-hash |
| Kerberos | AS-REQ credential validation, AS-REP Roasting, Kerberoasting |
| MySQL | Run SQL against MySQL / MariaDB, extract values, assert on results |
| MongoDB | Find/insert/update/delete/aggregate/count/run-command, extract a field, assert |
| PostgreSQL | Run SQL against PostgreSQL, extract values, assert on results |
Key concepts
Section titled “Key concepts”Six pieces, and the relationships between them matter more than any one of them. A probe is one protocol interaction. Bundles hold everything you author and carry its scope. Projects supply the values a run is aimed at. Chains put probes in order and pass results between them.
Probes
Section titled “Probes”A probe is a single protocol interaction. 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.
Bundles
Section titled “Bundles”A bundle is the container everything you author lives in: probes, chains, scripts, suites and skills. Every artifact belongs to exactly one bundle and takes its project scope from it. Bundles nest into a tree and can be linked to one or more projects. See Bundles.
Projects
Section titled “Projects”A project is a named scope: its environments, its credentials, and the bundles that belong to it. Set an active project to narrow the workspace to that work; the active project’s environment drives variable substitution in probes, chains and scripts.
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. Like every artifact, a chain lives in a bundle and takes its scope from it.
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 probes and chains without modifying their configuration.
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.