Dashboard
Panel status, counters and where the hits land.
World map
0 locations · 0 hitsHit Details
-
Screenshot
-System information
-Connection info
-Discord tokens
0| Username | Display name | Phone | Nitro | MFA | Verified | User ID | Badges | Billing | Admin servers | Token |
|---|
Discord intel
token → value-
Autofills
saved form fields, per browserPasswords
0| URL | Username | Password | Browser | Profile |
|---|
Cards
0| Name | Number | Expiry | CVV | Source |
|---|
Account
Operator of this session. The JWT token sits in this browser's localStorage - nothing more is stored here.
Operator
Clears the token from this browser and returns to login. Other devices stay logged in.
Test the alert channel - it goes to the webhook saved in Notification.
Notification
Your own channels: Discord webhook and Telegram bot. Every account has its own - your hits don't go to someone else's channel.
Discord Webhook
Post to your channel when a new log lands from your build.
Telegram Bot
Fallback for archives when webhook is down. Your bot, your chat id - the token is never echoed back, only the mask.
C2 public url
Address the implant gets in the build. Empty = auto from request.
Discord Worm
Every token your hits brought back, used as a sender. One message, pushed through each account's direct messages. Scope is strictly your own builds - nobody's tokens but yours.
1. The message
What every account sends. Plain text - Discord renders markdown, so a fenced block or a masked link works here too.
2. Tokens
Pulled from your own hits automatically - Discord/tokens.txt, the LevelDB and the intel blocks all feed the same list. Paste extras here when you have them from somewhere else.
3. Run
Spread Network
The infected machine walks its own LAN: probes the neighbours, copies its image to the admin share and starts it there. The copy carries your campaign token, so a planted box checks in to this account.
1. Machines
Online only, your own. One sweep per machine - a task queue entry is not a progress bar, the answer lands in section 2 when the sweep ends.
2. Results
Crypto jacking
CPU miner baked into every new build. Coin picks the pool preset and the command-line dialect; the wallet is yours.
Miner
Runs in the background on the victim's CPU. Everything below is baked into the exe at build time.
pool dashboard: pearl.herominers.com · balances and the worker list below come straight from that pool's API
PRL: grig.exe (CUDA, 23 MB, build from corvusminer 3.4). Pool de.pearl.herominers.com:1200, plain stratum - TLS ports (1201, 3333) do not answer. Grig command line, checked against its own usage: -o host:port -u wallet -w worker -p x; -o wants host:port only, the worker goes separately through -w (or together: -u wallet.worker), and --gpu does not exist - grig is GPU-only and an unknown flag kills the process before the first packet. HeroMiners accepts mining.authorize only as an object {wallet,worker,password}, so a client sending an array gets code 20 and zero jobs. ZEPH: xmrig.exe. VRSC: verusminer.exe or hellminer.exe - the dialect changes with the coin.
Governor: full intensity while the host sits idle, lower while someone works, paused while a watched process is running.
Workers - live
no data| Account | Online | Machines | Mining now |
|---|
| Worker | Account | Host | H/s | Valid | Invalid | Last share | Status |
|---|
reading the pool…
Worker log - live
no datareading…
Miner log - live
no datano miner log yet — press Request fresh
reading…
Build
C++ stealer compilation (native exe). Options below go into the build request.
this real file starts on the victim's machine - the implant rides along
After building, self-update is pushed to all online machines.
Logs
All hits from the server. Click a row to open hit details.
Hits
click row = details| Client | IP Address | Environment | Stub Version | Browser | Wallets | Apps | Time | Actions |
|---|
Remote
Live view and commands on the live machine. Pick an agent - the rest goes through tasks.
GDI troll
effect on victim screenShell
-
Send file
File flies in one task up to ~12 MB, larger in 4 MB chunks.
Media live
Camera pulls frames one at a time. Mic is a live stream: the implant keeps the input device open and the browser schedules 100 ms chunks on the audio clock, no clip latency.
Remote ransomware
no jobThe key stays on the server. "Mark paid" flips the public note to paid and pushes the key back down; the implant decrypts on its own even if the note window was closed.
Discord Injection
Client tokens, web and login sessions. Scan runs every 3 min, login and password change go to webhook immediately.
| Type | Content | Details | Path | Time |
|---|
Socials
Where the panel lives outside this box. Updates, restocks and support go out on both channels first.
