Amdocssims
Table of Contents
Overview
Amdocssims (classified in antivirus detection telemetry under designations including Trojan:Win32/Amdocssims, Trojan.Win32.Amdocssims, and Win32/Amdocssims) is a multi-stage trojan engineered to disguise itself as legitimate software, execute unauthorized commands, and coordinate with external command-and-control infrastructure. Disseminated across enterprise networks and consumer workstations via social engineering, phishing attachments, malicious drive-by downloads, or weaponized software cracks, Amdocssims 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 deceptive executable masquerading, registry run key autostart, system telemetry gathering, and remote C2 beaconing. 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:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1125 | Video/Audio Capture | Collection | ATT&CK ↗ |
T1040 | Network Sniffing (Stealing credentials in transit) | Credential Access | ATT&CK ↗ |
T1055 | Process Injection | Defense Evasion | ATT&CK ↗ |
T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder | Persistence | ATT&CK ↗ |
T1105 | Ingress Tool Transfer | Command and Control | ATT&CK ↗ |
T1082 | System Information Discovery | Discovery | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
- T1125: Restrict access to local camera or microphone APIs. Utilize endpoint protection that monitors hardware access.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-NSA | Network Sniffing Detection | Detect | T1040 | Audit promiscuous mode network interface state changes and enforce end-to-end internal traffic encryption. |
D3-PIAD | Process Injection Analysis & Detection | Detect | T1055 | Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC). |
D3-SDA | System Discovery Analysis | Detect | T1082 | Alert on rapid enumerations of systeminfo, hostname, and registry hardware trees in short intervals. |
D3-NTI | Network Traffic Inspection | Detect | T1105 | Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols. |
D3-HAC | Hardware Device Access Control | Isolate | T1125 | Enforce Group Policy hardware access restrictions on integrated webcams and microphones. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
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_AMDOCSSIMS_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Amdocssims"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "amdocssims" ascii wide nocase
$s2 = "riskware.amdocssims" ascii wide nocase
$s3 = "hacktool.telecom" ascii wide nocase
$s4 = "pup.amdocs" ascii wide nocase
$s5 = "trojan:win32/amdocssims" ascii wide nocase
$s6 = "trojan.win32.amdocssims" ascii wide nocase
$s7 = "win32/amdocssims" 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 - Amdocssims (Trojan) Execution & Triage
id: 04805116-a938-5834-92b9-941b3497611e
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Amdocssims 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/amdocssims
- 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_003
- attack.t1027
- attack.t1547_001
- attack.t1071_001
- attack.t1105
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
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_AMDOCSSIMS_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Amdocssims 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 = "amdocssims" 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.
- Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Amdocssims from retrieving secondary stage payloads.
- Capture process memory triage to detect and terminate malicious threads injected by Amdocssims into legitimate system processes such as explorer.exe or svchost.exe.
- Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Amdocssims persistence hooks.
- Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
- Rotate all credentials, domain user passwords, and session cookies active on the system during the Amdocssims execution timeframe.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the incident is resolved simply because an antivirus tool removed the initial Amdocssims dropper; always verify that secondary payloads and persistence hooks have been eradicated.
- Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Amdocssims until memory triage is complete.
- Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.
References & External Analysis
- Microsoft Defender Threat Encyclopedia - Trojan:Win32/Amdocssims
- Kaspersky Threat Intelligence - Trojan.Win32.Amdocssims
- MITRE ATT&CK - Enterprise Techniques
- Search "amdocssims" on VirusTotal (External Analysis)
- Search "amdocssims" on Any.Run (Sandbox Sandbox)
- Search "amdocssims" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Trojan:Win32/Amdocssims?
Amdocssims is a trojan threat designed to infiltrate Windows systems and execute unauthorized operations without user consent.
How does Amdocssims compromise target systems?
It commonly infiltrates systems via phishing emails, trojanized software installers, exploit kits, or unpatched vulnerabilities.
What persistence mechanisms does Amdocssims 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 Amdocssims 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 Amdocssims?
Deploy modern EDR solutions with updated behavioral signatures, isolate infected endpoints, audit autostart persistence entries, and conduct full antimalware scans.
How do I remove Amdocssims from Windows?
Manual removal of Amdocssims 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 Amdocssims infection?
Symptoms of Amdocssims 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 Trojans
Want to prevent Amdocssims 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/amdocssims.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.