How r0ttenbeef/vortex-stealer works
1. Repository purpose and runtime
- This is a Windows-focused Golang info-stealer / remote-control implant.
- It is built on Linux using Go + mingw, with Windows resource files (.syso) included for packaging.
2. Top-level orchestration
- main.go is the entrypoint and appears to coordinate startup, configuration loading, environment checks, installation/persistence, and the main collection/exfiltration loop.
- The README indicates the bot token and chat ID are stored encrypted, then decoded at runtime.
3. Command-and-control channel
- telehandler/ is the C2 layer.
- It maps Telegram bot commands into actions on a target host: health checks, screenshots, file collection, upload toggles, download-and-execute, and upgrade behavior.
- This is the main operator-facing control plane and the primary boundary between the implant and the outside world.
4. Data exfiltration pipeline
- datatransfer/ is the outbound delivery path for stolen artifacts.
- The README suggests exfiltration is via Telegram and also includes a file-hosting style uploader (gofile.go), so the architecture supports more than one output path.
- Collected data is likely packaged first, then transferred through this module.
5. Host profiling and targeting
- opsysinfo/ gathers endpoint metadata such as OS and system flags.
- hutil/ contains shared helpers for process inspection, counters, and archive/file handling.
- Together these form the “victim fingerprinting” layer used to identify the host and steer later actions.
6. Anti-analysis and AV evasion
- antiav/ and envtype/ implement defensive-evasion logic.
- envtype/ covers VM, sandbox, and analysis-environment detection using checks for platforms like VMware, VirtualBox, Xen, KVM, Hyper-V-like environments, and suspicious analytics/debug processes.
- antiav/ includes Windows security interference checks such as AV/Defender/UAC-related logic.
7. Artifact collection modules
- browser/ extracts browser data from Chromium and Gecko families, likely including profiles, cookies, and extension data.
- cryptowallets/ targets crypto wallet artifacts, especially browser extension wallets.
- messenger/ targets chat apps such as Discord, Telegram, Signal, Skype, Element, and WhatsApp.
- softwares/ targets common desktop tools like FileZilla, PuTTY, Steam, TeamViewer, Uplay, and WinSCP.
- vpn/ targets VPN client configs and data for NordVPN, OpenVPN, and ProtonVPN.
- wifi/ suggests local wireless credential collection.
8. Packaging and encryption
- encrypt/ is the crypto layer used to protect configuration and likely payloads or exfiltrated data.
- hutil/zipdir.go indicates collected files are probably archived before transfer.
- This forms a “collect → package → encrypt → send” data path.
9. Installation and persistence
- install/ likely handles deployment behavior such as copying the binary, setting startup/persistence, or renaming the implant.
- The README’s /upgrade and /drop commands imply the implant can receive and run updated components or secondary payloads.
10. Build and packaging boundary
- Makefile drives release builds for multiple Windows targets.
- rsrc_windows_*.syso and the images/ directory indicate embedded Windows resources/icons for the final binary.
- The project is organized as a modular implant: C2 + anti-analysis + collection plugins + exfiltration + installation.
Main entry points: cmdhandler.go Cmd dispatch · main.go Main · hutil.go Helpers · dataexfil.go Exfil pipeline
Components 19
Core runtime
Startup, coordination, install, and shared helpers
- Main · Bootstraps config, checks host state, and starts the implant loop
main.go - Install · Deploys the implant and handles installation-style behavior
install/install.go - Host info · Gathers OS and system metadata used for targeting and branching
opsysinfo/opsysinfo.go - Helpers · Common process, counter, and archive/file helpers
hutil/hutil.go
C2 control
Operator command handling and action dispatch
- Telegram C2 · Maps Telegram commands into host actions and operator control
telehandler/telehandler.go - Cmd dispatch · Interprets operator commands and routes them to actions
telehandler/cmdhandler.go - Capabilities · Defines available command features and command coverage
telehandler/cmdcaps.go
Evasion
Environment and security checks used before/during execution
- Env checks · Detects virtual machines, sandboxes, and analysis environments
envtype/vmtype.go - AV checks · Checks for Defender, AV, and UAC-related interference
antiav/avproc.go
Collection plugins
Modules that harvest host artifacts
- Browser data · Harvests Chromium and Gecko browser profiles and secrets
browser/browserdump.go - Wallets · Targets crypto wallet artifacts and extension wallets
cryptowallets/crypto.go - Messengers · Extracts data from chat and messaging apps
messenger/telegram.go - Desktop tools · Collects data from file transfer, remote access, and game clients
softwares/filezilla.go - VPN data · Targets VPN client configuration and credentials
vpn/openvpn.go - Wi‑Fi data · Collects local wireless credential material
wifi/wifi.go
Exfiltration
Packaging and outbound transfer of collected data
- Crypto · Protects configuration and likely packaged payloads or output
encrypt/encrypt.go - Exfil pipeline · Packages collected data and sends it through the chosen outbound path
telehandler/dataexfil.go - Transfer · Outbound delivery layer for stolen artifacts
datatransfer/datatransfer.go - File host · Alternate upload path for moving files off the host
datatransfer/gofile.go
Connections 27
- Main → Host info: profile host · Collect system metadata before doing other work
- Main → Env checks: detect analysis · Avoid suspicious virtualized or sandboxed environments
- Main → AV checks: check defenses · Assess security software and elevation constraints
- Main → Install: deploy · Handle setup, copying, or persistence behavior
- Main → Telegram C2: start C2 · Bring up the operator command channel
- Main → Exfil pipeline: run pipeline · Start packaging and outbound transfer of harvested data
- Main → Crypto: load crypto · Decode protected configuration and protect data at runtime
- Telegram C2 → Cmd dispatch: dispatch · Route incoming Telegram commands to local actions
- Telegram C2 → Capabilities: expose actions · Define available operator capabilities
- Cmd dispatch → Browser data: collect browser · Trigger browser artifact harvesting
- Cmd dispatch → Wallets: collect wallets · Trigger wallet artifact harvesting
- Cmd dispatch → Messengers: collect chats · Trigger messenger data harvesting
- Cmd dispatch → Desktop tools: collect tools · Trigger desktop tool artifact harvesting
- Cmd dispatch → VPN data: collect vpn · Trigger VPN artifact harvesting
- Cmd dispatch → Wi‑Fi data: collect wifi · Trigger wireless credential collection
- Cmd dispatch → Exfil pipeline: exfiltrate · Send collected artifacts onward for packaging and transfer
- Exfil pipeline → Helpers: archive data · Use shared archive and file helpers to package output
- Exfil pipeline → Crypto: protect data · Encrypt configuration or collected payloads before sending
- Exfil pipeline → Transfer: send · Hand off to outbound delivery layer
- Transfer → File host: alternate upload · Use file-hosting style upload when configured
- Browser data → Helpers: use helpers · Reuse shared file, process, and archive utilities
- Wallets → Helpers: use helpers · Reuse shared file and archive utilities
- Messengers → Helpers: use helpers · Reuse shared file and process utilities
- Desktop tools → Helpers: use helpers · Reuse shared collection and file helpers
- VPN data → Helpers: use helpers · Reuse shared file and config helpers
- Wi‑Fi data → Helpers: use helpers · Reuse shared host and file helpers
- Env checks → AV checks: gate execution · Suspicious environments feed defensive-evasion decisions