Kovter

Overview

Kovter is an extraordinarily evasive, polymorphic malware strain first detected in 2013. Initially engineered as a screen-locking police-impersonation ransomware, Kovter underwent a radical architectural evolution in 2014-2015, transitioning into a stealthy ad-fraud engine that pioneered 'fileless' registry-resident persistence on Microsoft Windows systems. Kovter achieves complete fileless execution by storing its primary encrypted payload directly within randomly named or unprintable binary registry keys. It establishes persistence via shell spawning shortcuts or registry Run keys that invoke mshta.exe or rundll32.exe, which in turn launch obfuscated PowerShell commands that decode shellcode straight into system RAM. In November 2018, the United States Department of Justice (Eastern District of New York) unsealed major indictments against Russian cybercriminals tied to the 3ve and Methbot botnet rings, confirming Kovter's central role in compromising over 1.7 million computers to generate tens of millions of dollars in fraudulent ad revenue.

Known aliases

Threat reports may refer to this family under multiple names:

• Kovter
• Trojan.Kovter
• Win32/Kovter
• Kovter Clicker

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

• 3ve / Methbot Cybercrime Syndicate (EDNY Indictments) High confidence
  Basis: Indictments unsealed by the US Department of Justice (EDNY) in November 2018 against Aleksandr Zhukov, Sergey Ovsyannikov, and six co-conspirators for operating the 3ve digital advertising fraud ring, which weaponized Kovter across millions of hosts. [source]

Family Pedigree & Lineage

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

Known Derivatives & Downstream Variants: Kovter Police Ransomware (2013) · Kovter Clickfraud Loader (2015) · Kovter Fileless Powershell (2016-2020)

MITRE ATT&CK Techniques

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

Tactical Mitigations

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

• T1059.001: Restrict execution of PowerShell. Enforce PowerShell Constrained Language Mode and Script Block Logging.
• T1059.005: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.

MITRE D3FEND™ Defensive Countermeasures

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

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

• CVE-2015-5119 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).
• CVE-2017-0199 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

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.

• 4f2e96d2ff86e7a2df25b84c8a29a6cf7d853177699317585f6e80b27ef3e6ff
• 9e49c7161bcf76ee8a20da62fecbf9bb748a31a98059bf4ce126ecba95f002f1

Delivery vectors

• Malvertising campaigns leveraging compromised web ad networks
• Phishing campaigns distributing ZIP files containing obfuscated JavaScript or Batch downloaders
• Secondary payload deployment from exploit kits exploiting Flash (CVE-2015-5119) and Office (CVE-2017-0199)

Persistence mechanisms

• Encrypted binary shellcode stored inside hidden or unprintable registry keys under HKCU\Software\Classes
• Autorun entry invoking mshta.exe or rundll32.exe executing inline JavaScript/PowerShell to launch memory shellcode

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:

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

title: SystemHelpDesk Detection - Kovter (Trojan) Execution & Triage
id: dc205370-6495-547b-997c-194ee920eeba
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Kovter malware family. Detects suspicious execution from temporary user
  directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/kovter
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_001
- attack.t1059_005
- attack.t1112
- attack.t1547_001
- attack.t1055_012
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

rule MALWARE_WIN_KOVTER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Kovter 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 = "kovter" 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
}

Containment & Response Steps

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

1. Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Kovter from retrieving secondary stage payloads.
2. Capture process memory triage to detect and terminate malicious threads injected by Kovter into legitimate system processes such as explorer.exe or svchost.exe.
3. Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Kovter persistence hooks.
4. Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
5. Rotate all credentials, domain user passwords, and session cookies active on the system during the Kovter execution timeframe.

What to Avoid

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

1. Do not assume the incident is resolved simply because an antivirus tool removed the initial Kovter dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Kovter until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

• US DOJ EDNY 3ve and Methbot Cybercrime Ring Indictments
• CISA Alert - Kovter Malware Technical Analysis
• MITRE ATT&CK - Kovter (S0180)
• Search "kovter" on VirusTotal (External Analysis)
• Search "kovter" on Any.Run (Sandbox Sandbox)
• Search "kovter" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Trojan)

Explore other documented threats in the same operational category:

• Wintrim
• Faketool
• Gampass
• Memery
• Lmkfrhivlcfba
• Ircfast
• Bankoren
• Dexel

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/kovter.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.