A_311_Death

Category: banking_trojan · Aliases: Haxdoor, A-311, Trojan.Haxdoor.A311 · Sample count (EMBER 2018): 0 · Enrichment: curated_sourced · Updated: 2026-08-01
Category: Banking_TrojanSeverity: HIGHStatus: Automated SignaturePlatform: WINDOWS_PEStage: Initial Access, Execution, Credential AccessFirst seen: 2005Motivation: Financial Theft🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
A-311 Death is a seminal Remote Administration Tool (RAT) and Trojan active during the early-to-mid 2000s threat landscape.

Table of Contents

Overview

A-311 Death is a seminal Remote Administration Tool (RAT) and Trojan active during the early-to-mid 2000s threat landscape. Operating primarily as an invasive stealth backdoor, it afforded remote operators unconstrained interactive control over compromised Windows endpoints. Architecturally, A-311 Death evolved from basic client-server administrative sockets into an advanced credential-harvesting weapon, introducing form-grabbing routines targeting web browser sessions, Transaction Authentication Number (TAN) interception for banking fraud, and inline HTTP redirection mechanisms designed for banking phishing attacks. Multiple threat researchers correlate A-311 Death directly with the emergence of the notorious Haxdoor malware family, frequently identifying it as the foundational toolkit and builder from which Haxdoor variants branched. The trojan exhibited custom rootkit cloaking features to mask its process image and disk artifacts, and famously issued the greeting string 'A-311 Death welcome' across established C2 sessions upon client authentication. Distributed commercially across underground forums in Standard, Full, and Ultimate tiers, A-311 Death stood as one of the earliest commercial precursors to modern Malware-as-a-Service (MaaS) crime kits.

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: Haxdoor_Banking_Rootkit

Known Derivatives & Downstream Variants: Haxdoor.A311 · A-311_Death_Trojan · Goldun

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-SEAScript Execution AnalysisDetectT1059Analyze script block syntax and command arguments at runtime to detect malicious automation.
D3-RVMRegistry Value Modification AnalysisDetectT1112Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings.

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_A_311_DEATH_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for A_311_Death"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "a_311_death" ascii wide nocase
        $s2 = "haxdoor" ascii wide nocase
        $s3 = "a-311" ascii wide nocase
        $s4 = "trojan.haxdoor.a311" 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 - A_311_death (Banking Trojan) Execution & Triage
id: 8cffd518-0c8e-5ca3-bbca-b5796f3d04a4
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the A_311_death malware family. Detects recon staging, certutil file payload
  staging, and web-inject process proxying characteristic of banking trojan initial
  loaders.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/a_311_death
- https://malware-families-catalog.systemhelpdesk.com/defensive/banking-trojan-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.banking-trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059
- attack.t1055
- attack.t1056_001
- attack.t1112
- attack.t1569
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \svchost.exe
    - \explorer.exe
    - \msiexec.exe
    - \certutil.exe
    CommandLine|contains:
    - -urlcache
    - -split -f
    - ipconfig /all
    - route print
    - netstat -ano
  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_A_311_DEATH_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for A_311_Death 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 = "a_311_death" 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 compromised hosts from network segments to sever active command sockets and prevent exfiltration.
  2. Terminate spawned backdoor binaries and inspect hook DLLs injected into explorer.exe or browser processes.
  3. Scrub malicious registry autorun entries in HKLM\Software\Microsoft\Windows\CurrentVersion\Run and system service registrations.
  4. Reset all financial, administrative, and domain credentials accessed from the impacted workstation.

What to Avoid

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

  1. Do not execute system recovery without memory triage, as rootkit components will evade basic file-system scanning.
  2. Do not access production banking or administrative portals until full operating system re-imaging is confirmed.

References & External Analysis

Frequently Asked Questions

What is A-311 Death?

A-311 Death is a historical Remote Access Trojan and backdoor from the early 2000s designed for unauthorized remote administration and financial credential theft.

How did A-311 Death compromise endpoints?

It was distributed via malicious attachments, cracked underground utilities, and web exploit droppers, installing stealth background listeners.

What is the relationship between A-311 Death and Haxdoor?

A-311 Death served as an early build framework and core codebase precursor for the notorious Haxdoor banking trojan family.

What specific theft capabilities did A-311 Death possess?

It pioneered browser form-grabbing, banking TAN code interception, keystroke logging, and hidden rootkit process concealment.

How was A-311 Death monetized by its developers?

It was sold as a commercial malware toolkit across early hacker forums in Standard, Full, and Ultimate editions, pioneering Malware-as-a-Service.

How do I remove A_311_Death from Windows?

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

Symptoms of A_311_Death 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 Banking_Trojans

Want to prevent A_311_Death and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan 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/a_311_death.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.