Executive Overview — What We’re Dealing With

This specimen has persisted long enough to matter. Human experts classified it as Malware, and the telemetry confirms a capable, evasive Trojan with real impact potential.

Extended Dwell Time Impact

For 17+ hours, this malware remained undetected — a half-day window that permitted the adversary to complete initial execution, establish basic persistence, and perform initial system enumeration.

Global Detection Posture — Who Caught It, Who Missed It

VirusTotal engines: 73. Detected as malicious: 58. Missed: 15. Coverage: 79.5%.

Why it matters: if any endpoint relies solely on a missed engine, this malware can operate with zero alerts. Prevention‑first controls close that gap regardless of signature lag.

Behavioral Storyline — How the Malware Operates

Significant process manipulation (34.46% of behavior) suggests code injection, process hollowing, or privilege escalation techniques. The malware is actively compromising running processes to hide its activities.

MITRE ATT&CK Mapping

• T1027 – encode data using Base64
• T1620 – invoke .NET assembly method
• T1620 – load .NET assembly
• T1003 – Accessed credential storage registry keys
• T1539 – Touches a file containing cookies, possibly for information gathering
• T1547 – Installs itself for autorun at Windows startup
• T1547.001 – Installs itself for autorun at Windows startup
• T1564 – A process created a hidden window
• T1202 – Uses Windows utilities for basic functionality
• T1202 – Uses suspicious command line tools or Windows utilities
• T1562 – Attempts to modify Windows Defender using PowerShell
• T1070.006 – Executable is attempted to be downloaded from an IP
• T1070.006 – Reads from the memory of another process
• T1070.006 – Makes a suspicious HTTP request to a commonly exploitable directory with questionable file ext
• T1070.006 – Yara detections observed in process dumps, payloads or dropped files
• T1070.006 – Attempts to connect to a dead IP:Port
• T1070.006 – At least one IP Address, Domain, or File Name was found in a crypto call
• T1070.006 – Resolves a suspicious Top Level Domain (TLD)
• T1112 – Installs itself for autorun at Windows startup
• T1112 – Stores JavaScript or a script command in the registry, likely for fileless persistence
• T1070 – Executable is attempted to be downloaded from an IP
• T1070 – Reads from the memory of another process
• T1070 – Makes a suspicious HTTP request to a commonly exploitable directory with questionable file ext
• T1070 – Deletes executed files from disk
• T1070 – Yara detections observed in process dumps, payloads or dropped files
• T1070 – Attempts to connect to a dead IP:Port
• T1070 – At least one IP Address, Domain, or File Name was found in a crypto call
• T1070 – Resolves a suspicious Top Level Domain (TLD)
• T1064 – Attempts to execute suspicious powershell command arguments
• T1064 – A scripting utility was executed
• T1497 – Checks the version of Bios, possibly for anti-virtualization
• T1497 – Detects VirtualBox through the presence of a registry key
• T1562.001 – Attempts to modify Windows Defender using PowerShell
• T1027 – The binary likely contains encrypted or compressed data
• T1564.003 – A process created a hidden window
• T1027.002 – The binary likely contains encrypted or compressed data
• T1082 – Checks the version of Bios, possibly for anti-virtualization
• T1082 – Checks available memory
• T1082 – Access the NetLogon registry key, potentially used for discovery or tampering
• T1010 – Checks for the presence of known windows from debuggers and forensic tools
• T1083 – Attempts to identify installed AV products by installation directory
• T1083 – Checks for the presence of known devices from debuggers and forensic tools
• T1057 – Enumerates the modules from a process (may be used to locate base addresses in process injection)
• T1057 – Checks for the presence of known windows from debuggers and forensic tools
• T1057 – Checks for the presence of known devices from debuggers and forensic tools
• T1057 – Checks the version of Bios, possibly for anti-virtualization
• T1057 – Expresses interest in specific running processes
• T1057 – Detects VirtualBox through the presence of a registry key
• T1057 – Detects the presence of Wine emulator via registry key
• T1012 – Checks the version of Bios, possibly for anti-virtualization
• T1012 – Access the NetLogon registry key, potentially used for discovery or tampering
• T1012 – Detects VirtualBox through the presence of a registry key
• T1012 – Detects the presence of Wine emulator via registry key
• T1518.001 – Attempts to identify installed AV products by installation directory
• T1518 – Detects the presence of Wine emulator via registry key
• T1518 – Attempts to identify installed AV products by installation directory
• T1071 – Executable is attempted to be downloaded from an IP
• T1071 – Reads from the memory of another process
• T1071 – HTTP traffic contains suspicious features which may be indicative of malware related traffic
• T1071 – Makes a suspicious HTTP request to a commonly exploitable directory with questionable file ext
• T1071 – Performs HTTP requests potentially not found in PCAP.
• T1071 – Network activity contains more than one unique useragent.
• T1071 – Yara detections observed in process dumps, payloads or dropped files
• T1071 – Attempts to connect to a dead IP:Port
• T1071 – At least one IP Address, Domain, or File Name was found in a crypto call
• T1071 – Resolves a suspicious Top Level Domain (TLD)
• T1573 – Establishes an encrypted HTTPS connection
• T1106 – Guard pages use detected – possible anti-debugging.
• T1059 – Attempts to modify Windows Defender using PowerShell
• T1059 – Attempts to execute suspicious powershell command arguments
• T1059 – Stores JavaScript or a script command in the registry, likely for fileless persistence
• T1059 – A scripting utility was executed
• T1059.001 – Attempts to execute suspicious powershell command arguments
• T1007 – Collects information about services
• T1010 – Tries to detect debugger
• T1012 – Tries to detect virtual machine
• T1016 – Queries a host’s domain name
• T1027.002 – Obfuscates control flow
• T1027.002 – Resolves API functions dynamically
• T1053.005 – Schedules task
• T1057 – Enumerates running processes
• T1059.001 – Bypasses PowerShell execution policy
• T1106 – Tries to evade debugger
• T1106 – Makes direct system call to possibly evade hooking based monitoring
• T1112 – Installs system service
• T1124 – Tries to detect virtual machine
• T1480 – Known malicious mutex name is created
• T1497 – Creates an unusually large number of processes
• T1497.001 – Tries to detect virtual machine
• T1497.003 – Tries to detect virtual machine
• T1518.001 – Tries to detect the presence of antivirus software
• T1543.003 – Installs system service
• T1562.001 – Modifies native system functions
• T1564.003 – Creates process with hidden window
• T1574.011 – Hijack installed services
• T1574.011 – Installs system service
• T1622 – Tries to detect debugger
• T1622 – Tries to evade debugger
• T1129 – The process attempted to dynamically load a malicious function
• T1059 – Detected command line output monitoring
• T1129 – The process tried to load dynamically one or more functions.
• T1564.003 – Detected the creation of a hidden window (common execution hiding technique)
• T1057 – The process has tried to detect the debugger probing the use of page guards.
• T1057 – The process may have looked for a particular process running on the system
• T1027.009 – The process has executed a dropped binary
• T1071 – Detected one or more anomalous HTTP requests
• T1071 – Detected HTTP requests to some non white-listed domains
• T1057 – The process attempted to detect a running debugger using common APIs
• T1119 – The process tried to detect the presence of common debug and forensic utilities
• T1063 – The process tried to detect the presence of common debug and forensic utilities
• T1082 – Queries for the computername
• T1063 – The process attempted to detect some widespread AVs presence looking at their installation directories
• T1119 – The process attempted to detect debuggers and common forensic/analysis tools looking for known devices
• T1063 – The process attempted to detect debuggers and common forensic/analysis tools looking for known devices
• T1082 – The process has tried to retrieve the BIOS version (maybe for checking the virtualization presence)
• T1012 – The process has tried to retrieve the BIOS version (maybe for checking the virtualization presence)
• T1086 – Detected some PowerShell commands executions
• T1060 – The process has tried to set its autorun on the system startup
• T1050 – The process has tried to set its autorun on the system startup
• T1112 – The process has tried to set its autorun on the system startup
• T1027.009 – Drops interesting files and uses them
• T1574.010 – Uses cacls to modify the permissions of files
• T1036 – Drops files with a non matching file extension (content does not match to file extension)
• T1036 – Creates files inside the user directory
• T1497 – Allocates memory with a write watch (potentially for evading sandboxes)
• T1562.001 – Creates guard pages, often used to prevent reverse engineering and debugging
• T1027.002 – PE file has section (not .text) which is very likely to contain packed code (zlib compression ratio < 0.011)
• T1027.002 – Binary may include packed or crypted data
• T1027 – Binary may include packed or crypted data
• T1082 – Queries the volume information (name, serial number etc) of a device
• T1021.001 – Contains functionality to start a terminal service
• T1071 – C2 URLs / IPs found in malware configuration

Following the Trail — Network & DNS Activity

Outbound activity leans on reputable infrastructure (e.g., CDNs, cloud endpoints) to blend in. TLS sessions and
HTTP calls show routine beaconing and IP‑lookup behavior that can masquerade as normal browsing.

Hunting tip: alert on unknown binaries initiating TLS to IP‑lookup services or unusual CDN endpoints — especially early in execution.