T1090.001: Proxy: Internal Proxy
T1090.001 (Proxy: Internal Proxy) is classified under the Command and Control tactic within the MITRE ATT&CK framework. Communication channels and covert protocols utilized to maintain interactive control of compromised implants through legitimate web protocols, encrypted proxies, and DNS tunneling. In telemetry gathered across enterprise endpoints and the EMBER 2018 benchmark, this technique was weaponized across 4 distinct malware families, totaling over 20,731 validated samples.
Technical Anatomy & Adversary Tradecraft
Adversaries leverage Proxy: Internal Proxy to accomplish operational objectives while minimizing anomalous forensic footprints. When executing Proxy: Internal Proxy, malicious binaries commonly interact directly with low-level Windows APIs, kernel mode drivers, or native scripting interfaces to bypass traditional file-integrity monitors and static antivirus signatures.
In modern multi-stage campaigns, T1090.001 is frequently observed functioning as an intermediate bridge: initial access payloads (such as spearphishing loaders or exploit macros) execute Proxy: Internal Proxy to establish in-memory execution or persistence before staging secondary ransomware or data-exfiltration implants.
https://attack.mitre.org/techniques/T1090/001/.
Detection Engineering & Threat Hunting
Detecting Proxy: Internal Proxy requires telemetry correlation across endpoint detection and response (EDR) agents, Sysmon event streams, and security information event management (SIEM) pipelines:
- Process Creation & Lineage: Monitor parent-child process anomalies where unexpected parent binaries (e.g., Office executables, web browsers, or script hosts) spawn command shells or native Windows utilities.
- API Hooking & Behavioral Telemetry: EDR platforms should flag rapid calls to memory allocation, process injection, or registry manipulation APIs originating from unbacked executable memory regions.
- Network Anomaly Correlation: Cross-reference endpoint execution timestamps with external network socket establishment to identify anomalous beaconing or covert data staging.
SOC Containment & Hardening Guidance
To mitigate risks associated with T1090.001 (Proxy: Internal Proxy) across production infrastructure, security teams should implement the following defensive controls:
- Attack Surface Reduction (ASR): Enforce strict application control policies (WDAC or AppLocker) to restrict execution to signed and verified corporate binaries.
- Least Privilege & Credential Hygiene: Restrict local administrative privileges to prevent adversaries from tampering with defensive agents or escalating privileges.
- Network Microsegmentation: Restrict lateral communication across endpoint VLANs to prevent wormable payloads from utilizing Proxy: Internal Proxy across adjacent network segments.
Cataloged Malware Families Utilizing T1090.001 (4 Families)
The following malware families in the SystemHelpDesk catalog have been verified utilizing T1090.001 (Proxy: Internal Proxy):
| Family | Category | Sample Count | Technical Summary |
|---|---|---|---|
| sality | File Infector | 18,572 | Sality is one of the most durable, resilient, and historically significant polymorphic file infectors and botnets in cybersecurity history. First identified aro... |
| dotdo | Adware | 1,678 | Dotdo (tracked across enterprise antivirus vendors as Adware:Win32/Dotdo, Trojan:Win32/Dotdo, and Adware.DotDo) is a persistent adware engine and local network ... |
| berbew | Infostealer | 407 | Trojan:Win32/Berbew (widely known in antivirus telemetry as Padodor) is a historic banking trojan and multi-purpose infostealer discovered in 2004 that pioneere... |
| bayrob | Trojan | 74 | Bayrob (cataloged across cybersecurity research and international law enforcement filings as Trojan.Bayrob, Win32/Bayrob, and W32.Bayrob) was a notorious cyberc... |