Doubleagent

Category: advanced_threat · Aliases: HackTool.DoubleAgent, Exploit.ApplicationVerifier, Riskware.DoubleAgent · Sample count (EMBER 2018): 1 · Enrichment: expert-seo · Updated: 2026-10-15
Category: Advanced_ThreatStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceActor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Opportunistic🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
<h3>Executive Summary</h3> DoubleAgent is not a traditional malware family, but rather a highly sophisticated, open-source code injection and persistence technique.

Table of Contents

Overview

Executive Summary

DoubleAgent is not a traditional malware family, but rather a highly sophisticated, open-source code injection and persistence technique. It exploits a legitimate feature of the Windows operating system—the Application Verifier—to inject a malicious DLL into *any* process during its initialization. While originally documented by researchers as a proof-of-concept, the DoubleAgent technique is actively abused by advanced threat actors and APT groups to establish completely invisible persistence and bypass next-generation endpoint security controls.

Technical Architecture and Exploitation

The Windows Application Verifier is a developer tool designed to monitor applications for memory corruption and handle leaks. It works by loading a specific "verifier provider DLL" into the target process as it starts. The DoubleAgent technique abuses this mechanism:

Threat Impact

The DoubleAgent technique is a critical threat. It allows an attacker to gain full control over any application on the system. By injecting into the antivirus process itself, the attacker can silently neutralize the endpoint's primary defense mechanism, rendering it incapable of detecting subsequent malicious activity.

Defense and Resilience Strategies

Known aliases

Threat reports may refer to this family under multiple names:

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

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-DIADLL Injection AnalysisDetectT1055.001Monitor remote thread creation (CreateRemoteThread) and unauthorized DLL loading into core Windows processes (svchost.exe, explorer.exe).
D3-STASecurity Tool Anti-Tamper EnforcementHardenT1562.001Block unauthorized modification of antivirus registry flags and prevent stopping security agent services.

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_DOUBLEAGENT_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Doubleagent"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "doubleagent" ascii wide nocase
        $s2 = "hacktool.doubleagent" ascii wide nocase
        $s3 = "exploit.applicationverifier" ascii wide nocase
        $s4 = "riskware.doubleagent" 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 - Doubleagent (Advanced Threat) Execution & Triage
id: 47c06d01-94bd-583d-9be6-1bf3f6b7e2b4
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Doubleagent malware family. Detects proxy execution, reflective DLL loading,
  and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/doubleagent
- 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.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1546_012
- attack.t1055_001
- attack.t1562_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \powershell.exe
    - \cmd.exe
    - \rundll32.exe
    - \regsvr32.exe
    CommandLine|contains:
    - DownloadString
    - IEX(
    - '/s /n /u /i:'
    - sc create
    - start-process
  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_DOUBLEAGENT_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Doubleagent 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 = "doubleagent" 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. Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Doubleagent adversary activity.
  2. Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Doubleagent C2 infrastructure IP/domain lists.
  3. Review Active Directory domain controller authentication logs for anomalous Kerberos ticket requests (Pass-the-Ticket, Golden Ticket) and unauthorized DCSync operations associated with Doubleagent.
  4. Block all confirmed C2 domains, dynamic DNS endpoints, and proxy IP addresses across perimeter firewalls, proxies, and DNS security gateways.
  5. Conduct an enterprise-wide sweep across surrounding subnets for secondary webshells, WMI event subscriptions, or remote execution tooling left behind by Doubleagent operators.

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 Doubleagent 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 Doubleagent 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

Frequently Asked Questions

What is Doubleagent and what threat category does it belong to?

Doubleagent is classified as a Advanced Threat. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.

How does Doubleagent establish persistence and evade defensive controls?

Doubleagent typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.

What are the essential incident response steps for mitigating a Doubleagent compromise?

Security teams responding to Doubleagent should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.

What lateral movement and credential access tactics does HackTool.DoubleAgent leverage in enterprise intrusions?

HackTool.DoubleAgent frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers.

How does HackTool.DoubleAgent maintain covert communications and evade perimeter network monitoring?

HackTool.DoubleAgent often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering.

How do I remove Doubleagent from Windows?

Manual removal of Doubleagent 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 Doubleagent infection?

Symptoms of Doubleagent 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 Advanced_Threats

Want to prevent Doubleagent and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.

📣 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/doubleagent.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.