voidrat gives you a live command console: connected hosts, remote shell, file transfer, screen capture, credential logs, and a payload builder — all behind a single login.
No tabs, no external dashboards. The panel is the only window you need.
Hostname, user, OS, arch, geo, and last check-in. Online state derived from the heartbeat window, not a flag the agent can lie about.
Queue a command, get stdout back on the next poll. Tasks are per-client, idempotent, and expire cleanly.
Push and pull files with size caps enforced server-side. Chunked, resumable, checksummed on both ends.
Frame grab at a configurable rate. Encoded off-thread so the beacon never blocks the transport.
Browser stores, session tokens, and wallet files, zipped and tagged by campaign automatically.
Layer 4 and layer 7 test methods with per-plan concurrency limits and a live job queue.
Every record sits in an AES-256-GCM store keyed outside the database file. Session and agent tokens are stored as SHA-256 hashes, so a copied database cannot be replayed.
Standalone executable, sideloaded DLL, Fabric mod, or injection into an existing jar. Campaign tags and padding on every format.
Self-contained Windows binary that pulls and runs the agent.
Drops next to a signed host and loads on launch.
Drop-in Fabric jar. Padding slider changes size and hash.
Upload a jar, get it back with the loader stitched in.
Every tier includes the builder and the agent channel. Limits scale with the plan.
Build a payload from the builder with your enrollment key baked in. On first run the agent calls /api/agent/register, gets a client ID and bearer token, and starts polling for tasks. It shows up in the client list within one check-in window.
It is generated per account and shown on the Account page. It authorizes new clients to register under your panel. Rotate it any time and existing clients keep working — only new registrations are rejected.
In a single JSON store next to the server binary, written atomically. Swap lib/db.js for Postgres or SQLite when you outgrow it; the query surface is six functions.
Yes. Sessions live in the same store with a seven-day TTL, so a restart keeps you signed in until the session expires.
That is the intended deployment. node server.js behind Cloudflare Tunnel needs no inbound port and no open firewall rule.
Create an account, copy your enrollment key, build the first payload.