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: 57. Missed: 16. Coverage: 78.1%.

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

Dominant system-level operations (56.35% of behavior) suggest this malware performs deep system reconnaissance, privilege escalation, or core OS manipulation. It’s actively probing system defenses and attempting to gain administrative control.

MITRE ATT&CK Mapping

• T1027 – encode data using XOR
• T1202 – Uses suspicious command line tools or Windows utilities
• T1202 – Uses Windows utilities for basic functionality
• T1562 – Tries to unhook or modify Windows functions monitored by CAPE
• T1562 – Attempts to stop active services
• T1112 – Installs itself for autorun at Windows startup
• T1112 – Installs itself for autorun at Windows startup
• T1070 – Deletes executed files from disk
• T1064 – Attempts to execute suspicious powershell command arguments
• T1064 – A scripting utility was executed
• T1497 – Detects VirtualBox through the presence of a registry key
• T1497 – Checks the version of Bios, possibly for anti-virtualization
• T1562.001 – Tries to unhook or modify Windows functions monitored by CAPE
• T1562.001 – Attempts to stop active services
• T1027 – The binary contains an unknown PE section name indicative of packing
• T1027 – The binary likely contains encrypted or compressed data
• T1027.002 – The binary contains an unknown PE section name indicative of packing
• T1027.002 – The binary likely contains encrypted or compressed data
• T1543 – Attempts to stop active services
• T1547 – Installs itself for autorun at Windows startup
• T1543.003 – Attempts to stop active services
• T1053 – Installs itself for autorun at Windows startup
• T1547.001 – Installs itself for autorun at Windows startup
• T1539 – Touches a file containing cookies, possibly for information gathering
• T1489 – Attempts to stop active services
• T1082 – Access the NetLogon registry key, potentially used for discovery or tampering
• T1082 – Checks the version of Bios, possibly for anti-virtualization
• T1082 – Checks available memory
• T1010 – Checks for the presence of known windows from debuggers and forensic tools
• T1083 – Checks for the presence of known devices from debuggers and forensic tools
• T1057 – Enumerates running processes
• T1057 – Detects the presence of Wine emulator via registry key
• T1057 – Checks for the presence of known devices from debuggers and forensic tools
• T1057 – Expresses interest in specific running processes
• T1057 – Checks the version of Bios, possibly for anti-virtualization
• T1057 – Detects VirtualBox through the presence of a registry key
• T1057 – Checks for the presence of known windows from debuggers and forensic tools
• T1012 – Detects VirtualBox through the presence of a registry key
• T1012 – 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
• T1518 – Detects the presence of Wine emulator via registry key
• T1071 – Terminates another process
• T1071 – Resolves a suspicious Top Level Domain (TLD)
• T1071 – Executable is attempted to be downloaded from an IP
• T1071 – At least one IP Address, Domain, or File Name was found in a crypto call
• T1071 – HTTP traffic contains suspicious features which may be indicative of malware related traffic
• T1071 – Reads from the memory of another process
• T1071 – Makes a suspicious HTTP request to a commonly exploitable directory with questionable file ext
• T1071 – Yara detections observed in process dumps, payloads or dropped files
• T1071 – Attempts to connect to a dead IP:Port
• T1573 – Establishes an encrypted HTTPS connection
• T1106 – Guard pages use detected – possible anti-debugging.
• T1059 – Attempts to execute suspicious powershell command arguments
• T1059 – A scripting utility was executed
• T1059.001 – Attempts to execute suspicious powershell command arguments
• T1129 – The process tried to load dynamically one or more functions.
• T1057 – The process may have looked for a particular process running on the system
• T1045 – Manalize Local SandBox Packer Harvesting
• T1027 – encode data using XOR
• T1057 – The process attempted to detect a running debugger using common APIs
• T1063 – The process tried to detect the presence of common debug and forensic utilities
• T1119 – The process tried to detect the presence of common debug and forensic utilities
• T1063 – The process attempted to detect debuggers and common forensic/analysis tools looking for known devices
• T1119 – The process attempted to detect debuggers and common forensic/analysis tools looking for known devices
• T1012 – The process has tried to retrieve the BIOS version (maybe for checking the virtualization presence)
• T1082 – The process has tried to retrieve the BIOS version (maybe for checking the virtualization presence)

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.