Darkkomet

Category: rat · Aliases: DarkComet, DarkComet RAT, DarkKomet, Trojan.DarkComet, Backdoor.Win32.DarkKomet · Sample count (EMBER 2018): 801 · Enrichment: curated_sourced · Updated: 2026-07-02T07:47:42Z
Category: RatStatus: Automated SignaturePlatform: WINDOWS_PEStage: Persistence, Command And Control, Remote AccessFirst seen: 2008Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Opportunistic🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
DarkComet (frequently cataloged in security telemetry as DarkKomet or Backdoor.Win32.DarkKomet) is an iconic, feature-packed Remote Access Trojan (RAT) originally authored in 2008 by independent French developer Jean-Pierre Lesueur (known online as 'DarkCoderSC').

Table of Contents

Overview

DarkComet (frequently cataloged in security telemetry as DarkKomet or Backdoor.Win32.DarkKomet) is an iconic, feature-packed Remote Access Trojan (RAT) originally authored in 2008 by independent French developer Jean-Pierre Lesueur (known online as 'DarkCoderSC'). Developed in Delphi, the tool boasted an intuitive graphical management console, low system resource utilization, and deep surveillance capabilities—including real-time audio and webcam surveillance, full keystroke logging, remote desktop streaming, reverse proxying, and file manipulation. Although originally marketed as a dual-use remote administration utility, DarkComet was aggressively weaponized by cybercriminals, hacktivists, and advanced persistent threat groups globally. Most notably between 2011 and 2014 during the Syrian Civil War, Syrian state-aligned threat actors deployed weaponized DarkComet builds embedded inside fake revolutionary PDF manifestos and Skype communications to target, track, and spy on anti-government dissidents, journalists, and activists. In response to mounting evidence that his software was being abused in human-rights violations, Lesueur publicly terminated the project in July 2012, releasing the 'DarkComet RAT Remover' cleanup utility. Leaked builder versions (notably v5.3.1) continue to be circulated and used in low-level cybercrime.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

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

→ Explore all Threat Actor & APT Campaign Profiles

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: Darkcomet V2.X · Darkcomet V3.X · Darkcomet V5.1 · Darkcomet V5.3.1 (Final Release)

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-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-SDScreen Capture DetectionDetectT1113Monitor desktop graphics API calls (BitBlt, GetDC) triggered by non-standard background threads.
D3-HACHardware Device Access ControlIsolateT1125Enforce Group Policy hardware access restrictions on integrated webcams and microphones.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

Exploited Vulnerabilities (CVEs)

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

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.

ProtocolsTCP, RC4-Encrypted Stream, Dynamic DNS Reverse Connection
Observed ports1604, 7777, 8888, 443
Infrastructure modelDynamic DNS domains (No-IP, DynDNS) communicating over raw TCP sockets using RC4 symmetric encryption with hardcoded keys specified during client compilation.
Identifiable from traffic aloneUnrated

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_DARKKOMET_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Darkkomet"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "darkkomet" ascii wide nocase
        $s2 = "darkcomet" ascii wide nocase
        $s3 = "darkcomet rat" ascii wide nocase
        $s4 = "darkkomet" ascii wide nocase
        $s5 = "trojan.darkcomet" ascii wide nocase
        $s6 = "backdoor.win32.darkkomet" 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 - Darkkomet (Rat) Execution & Triage
id: 8fe3e3e8-dc95-57c2-b06a-081197a102c2
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Darkkomet malware family. Detects unauthorized persistence creation via
  Windows Registry Run keys, scheduled tasks, and privilege escalation indicative
  of RAT installations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/darkkomet
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.rat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1056_001
- attack.t1113
- attack.t1125
- attack.t1071_001
- attack.t1547_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \reg.exe
    - \schtasks.exe
    - \cmd.exe
    - \powershell.exe
    CommandLine|contains:
    - \CurrentVersion\Run
    - /create /tn
    - bypass -enc
    - net user /add
    - net localgroup administrators
  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_DARKKOMET_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Darkkomet 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 = "darkkomet" 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. Immediately isolate the compromised host from internal LAN and WAN environments to cut off interactive remote shell sessions established by Darkkomet.
  2. Inspect active socket listeners and outbound established network connections ('netstat -ano') to identify and sever covert TCP/UDP channels used by Darkkomet.
  3. Scan Windows Services, Scheduled Tasks, and Startup folders to locate and eliminate persistent backdoor listeners configured by Darkkomet.
  4. Invalidate all active VPN profiles, local administrator credentials, and session tokens that may have been harvested by the Darkkomet operator.
  5. Re-image the affected host using a validated golden image prior to reconnecting it to enterprise network segments.

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 interact with or send messages through the Darkkomet remote terminal, as this alerts the attacker and may cause them to execute destructive anti-forensic commands.
  2. Avoid relying solely on static file signatures, as Darkkomet payloads frequently execute reflectively in memory without writing binaries to disk.

References & External Analysis

Frequently Asked Questions

What is DarkComet RAT?

DarkComet is a Delphi-based Remote Access Trojan created in 2008 by Jean-Pierre Lesueur that offers full remote desktop control, keylogging, and audio/webcam surveillance.

Why did the creator of DarkComet stop development?

Jean-Pierre Lesueur ceased development in 2012 after security researchers revealed that Syrian government actors were using DarkComet to spy on and locate political dissidents during the Syrian Civil War.

How does DarkComet communicate with its controller?

DarkComet establishes a persistent reverse TCP connection (default port 1604) protected with RC4 encryption using a key configured inside the builder.

What vulnerabilities were used to distribute DarkComet?

DarkComet was frequently dropped by malicious office documents exploiting buffer overflow vulnerabilities such as CVE-2010-3333 and CVE-2012-0158.

How can systems be cleaned of DarkComet?

Use updated endpoint detection to quarantine injected processes, delete persistence registry keys under Run and RunOnce, and scan memory with YARA rules matching DarkComet RC4 strings.

How do I remove Darkkomet from Windows?

Manual removal of Darkkomet 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.

What are the main symptoms of a Darkkomet infection?

Symptoms of Darkkomet 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 Rats

Want to prevent Darkkomet and similar threats from compromising your organization? Read our comprehensive defensive guide: Backdoor & RAT Protection for Businesses.

📣 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 team.

Machine-readable

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