Stantinko

Category: botnet · Aliases: Trojan:Win32/Stantinko, Win32/CoinMiner.Stantinko, Win64/CoinMiner.Stantinko, Trojan.Win32.Stantinko, Stantinko Botnet · Sample count (EMBER 2018): 168 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: BotnetStatus: Automated SignaturePlatform: WINDOWS_PEStage: Command And Control, Cryptomining, Credential Access, PersistenceFirst seen: 2012Actor: Stantinko Cybercriminal Operator GroupIndustry: Global / Opportunistic, E-Commerce, Web HostingMotivation: Financial Theft🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Stantinko (tracked across threat intelligence feeds as Trojan:Win32/Stantinko, Win32/CoinMiner.Stantinko, and Trojan.Win32.Stantinko) is a massive, highly resilient cybercriminal botnet documented extensively by ESET Research.

Table of Contents

Overview

Stantinko (tracked across threat intelligence feeds as Trojan:Win32/Stantinko, Win32/CoinMiner.Stantinko, and Trojan.Win32.Stantinko) is a massive, highly resilient cybercriminal botnet documented extensively by ESET Research. Active since at least 2012, Stantinko has compromised over 500,000 endpoints primarily across Russia, Ukraine, Belarus, and Kazakhstan. The botnet employs sophisticated multi-stage infection chains, distributing its modular dropper disguised as pirated software or cracked torrents. Once on an endpoint, Stantinko establishes mutual self-healing Windows services (e.g., udservice.exe); if one service is terminated or deleted, the sibling service immediately restores it. Stantinko's operators deploy diverse monetization modules, including installing malicious extensions from the Chrome Web Store (such as 'The Safe Surfing' and 'Teddy Protection') to execute click fraud and ad-injection, conducting social network account takeover, launching brute-force attacks against WordPress and Joomla administrator consoles, and mining Monero using heavily obfuscated, per-victim compiled xmr-stak cryptominers that resolve mining proxy IPs covertly encoded into YouTube video descriptions.

Known aliases

Threat reports may refer to this family under multiple names:

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Modular Botnet Architecture · Xmr-Stak Monero Cryptomining Framework

Known Derivatives & Downstream Variants: Coinminer.Stantinko · Teddy Protection Extension · Safe Surfing Extension

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-PSBLPowerShell Script Block LoggingDetectT1059.001Enable PowerShell event ID 4104 and Constrained Language Mode to neuter obfuscated script payloads.
D3-BEABrowser Extension AllowlistingHardenT1176Deploy enterprise browser policies via GPO or Intune to block unauthorized side-loaded extensions and add-ons.
D3-FEAFile Execution AnalysisHardenT1204.002Enforce AppLocker and Windows Defender Application Control (WDAC) to block executable launches from temporary and user-writable directories.
D3-PEAProcessor Execution AuditingDetectT1496Alert on sustained high CPU/GPU utilization by processes originating from temporary user directories and block stratum mining pool ports.

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

rule MALWARE_WIN_STANTINKO_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Stantinko"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "stantinko" ascii wide nocase
        $s2 = "trojan:win32/stantinko" ascii wide nocase
        $s3 = "win32/coinminer.stantinko" ascii wide nocase
        $s4 = "win64/coinminer.stantinko" ascii wide nocase
        $s5 = "trojan.win32.stantinko" ascii wide nocase
        $s6 = "stantinko botnet" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Stantinko (Botnet) Execution & Triage
id: f9439851-ef8f-5d73-aff2-5e27be2d039f
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Stantinko malware family. Detects firewall rule subversion, internal port
  proxying, and command-and-control keepalive polling indicative of botnet nodes.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/stantinko
- https://malware-families-catalog.systemhelpdesk.com/defensive/botnet-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.botnet
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1204_002
- attack.t1546_003
- attack.t1496
- attack.t1176
- attack.t1102_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \netsh.exe
    - \route.exe
    - \arp.exe
    - \ping.exe
    CommandLine|contains:
    - advfirewall firewall add rule
    - netsh interface portproxy
    - ping -n 1 127.0.0.1
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_STANTINKO_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Stantinko tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "stantinko" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Isolate the infected endpoint from the corporate network immediately to disrupt botnet C2 communications and cryptomining activity.
  2. Identify and simultaneously terminate both self-healing watchdog services (e.g., udservice.exe) to prevent automatic reinstallation.
  3. Purge rogue browser extensions installed via local Chrome policy keys (HKCU\Software\Policies\Google\Chrome).
  4. Due to Stantinko's deeply embedded rootkit components and encrypted registry payloads, re-imaging the operating system is strongly recommended.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not attempt to delete only one of the Stantinko Windows services, as the surviving watchdog will restore the removed service within seconds.
  2. Avoid downloading pirated software, cracked games, or torrent installers that serve as the primary distribution channel for Stantinko droppers.

References & External Analysis

Frequently Asked Questions

What is the Stantinko botnet?

Stantinko is a large-scale, modular botnet active since 2012 that engages in click fraud, cryptomining, and credential theft.

How does Stantinko achieve self-healing persistence?

It deploys two cross-monitoring Windows services that detect if the other is deleted and automatically reinstall it.

How does Stantinko conduct ad fraud and browser manipulation?

It installs rogue Google Chrome extensions (like 'Teddy Protection') that inject advertisements and manipulate search traffic.

How does Stantinko's cryptomining module evade detection?

It generates unique, source-level obfuscated binaries per victim and retrieves mining proxies from YouTube video descriptions.

How can an enterprise remediate a Stantinko infection?

Isolate the endpoint, terminate mutual watchdog services simultaneously, purge rogue browser extensions, and perform an OS reimage.

How do I remove the Stantinko Botnet from Windows?

Manual removal of Stantinko is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

Is Stantinko a virus or a Botnet?

Stantinko is classified as a Botnet. Unlike traditional viruses that infect files, modern malware like Stantinko typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Stantinko infection?

Symptoms of Stantinko can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Botnets

Want to prevent Stantinko and similar threats from compromising your organization? Read our comprehensive defensive guide: Botnet Protection & Remediation.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk Threat Intelligence Team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/stantinko.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.