Adduser

Category: backdoor · Aliases: Backdoor:Win32/Adduser, Backdoor.Win32.Adduser, Win32/Adduser · Sample count (EMBER 2018): 4 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: BackdoorStatus: Automated SignaturePlatform: WINDOWS_PEStage: Persistence, Command And Control, Remote AccessActor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Opportunistic🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Adduser (classified in antivirus detection telemetry under designations including Backdoor:Win32/Adduser, Backdoor.Win32.Adduser, and Win32/Adduser) is a interactive remote access trojan and backdoor providing remote threat actors with unauthorized terminal control, file manipulation, and surveillance.

Table of Contents

Overview

Adduser (classified in antivirus detection telemetry under designations including Backdoor:Win32/Adduser, Backdoor.Win32.Adduser, and Win32/Adduser) is a interactive remote access trojan and backdoor providing remote threat actors with unauthorized terminal control, file manipulation, and surveillance. Disseminated across enterprise networks and consumer workstations via social engineering, phishing attachments, malicious drive-by downloads, or weaponized software cracks, Adduser executes an initial reconnaissance phase upon system ingress. The binary evaluates host privileges, detects active hypervisors and sandbox environments to evade behavioral analysis, and establishes resilient autostart persistence by configuring registry keys under HKCU\Software\Microsoft\Windows\CurrentVersion\Run or registering background Windows services. Operational mechanics characteristic of this family include reverse shell connections, process hollowing, privilege escalation, and lateral movement reconnaissance. Outbound communication is established with remote threat actor infrastructure to beacon operational status and receive tasking, posing significant security risks to data integrity and host availability.

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

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-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.

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_ADDUSER_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Adduser"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "adduser" ascii wide nocase
        $s2 = "backdoor:win32/adduser" ascii wide nocase
        $s3 = "backdoor.win32.adduser" ascii wide nocase
        $s4 = "win32/adduser" 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 - Adduser (Backdoor) Execution & Triage
id: 8665ab40-ae44-5ade-9376-6752145843b2
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Adduser 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/adduser
- 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.backdoor
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_003
- attack.t1055
- attack.t1573
- attack.t1547_001
- attack.t1070
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_ADDUSER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Adduser 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 = "adduser" 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 disable (do not delete yet, for forensic purposes) any rogue accounts created by the tool.
  2. Isolate the endpoint where the command was executed; if the tool was run successfully, the attacker already has SYSTEM-level access to that machine.
  3. Audit all Active Directory and Local Administrator groups across the network to ensure no other unauthorized accounts have been created.
  4. Conduct a full root-cause analysis to determine how the attacker gained the initial administrative privileges required to run the Adduser tool.

What to Avoid

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

  1. Do not assume that deleting the rogue account removes the attacker; if they have `SYSTEM` access, they likely have deployed other backdoors (like scheduled tasks or web shells).
  2. Avoid ignoring alerts for `net.exe /add`; while sometimes used by legitimate IT scripts, it is one of the most common techniques used by ransomware operators and APTs to maintain access.

References & External Analysis

Frequently Asked Questions

What is Backdoor:Win32/Adduser?

Adduser is a backdoor threat designed to infiltrate Windows systems and execute unauthorized operations without user consent.

How does Adduser compromise target systems?

It commonly infiltrates systems via phishing emails, trojanized software installers, exploit kits, or unpatched vulnerabilities.

What persistence mechanisms does Adduser utilize?

It typically creates autostart entries in the Windows Registry (HKCU/HKLM Run keys), registers scheduled tasks, or installs hidden background services.

What risks does Adduser pose to an enterprise?

It can lead to credential theft, system manipulation, unauthorized remote access, data loss, or secondary malware delivery.

How can administrators detect and eliminate Adduser?

Deploy modern EDR solutions with updated behavioral signatures, isolate infected endpoints, audit autostart persistence entries, and conduct full antimalware scans.

How do I remove Adduser from Windows?

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

Symptoms of Adduser 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 Backdoors

Want to prevent Adduser 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 Threat Intelligence Team.

Machine-readable

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