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 2+ hours, this malware remained undetected — a limited but sufficient window for the adversary to complete initial execution and establish basic system access.

Global Detection Posture — Who Caught It, Who Missed It

VirusTotal engines: 73. Detected as malicious: 60. Missed: 13. Coverage: 82.2%.

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 (47.30% 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

• T1497.001 – reference anti-VM strings targeting VirtualBox
• T1562 – Tries to unhook or modify Windows functions monitored by CAPE
• 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
• 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
• T1082 – Checks available memory
• T1082 – Checks the version of Bios, possibly for anti-virtualization
• 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 – Checks for the presence of known windows from debuggers and forensic tools
• T1057 – Checks the version of Bios, possibly for anti-virtualization
• T1057 – Detects the presence of Wine emulator via registry key
• T1057 – Detects VirtualBox through the presence of a registry key
• T1057 – Checks for the presence of known devices from debuggers and forensic tools
• T1057 – Expresses interest in specific running processes
• T1057 – Enumerates running processes
• T1012 – Detects the presence of Wine emulator via registry key
• T1012 – Detects VirtualBox through the presence of a registry key
• T1012 – Checks the version of Bios, possibly for anti-virtualization
• T1518 – Detects the presence of Wine emulator via registry key
• T1071 – Yara detections observed in process dumps, payloads or dropped files
• T1071 – Attempts to connect to a dead IP:Port
• T1071 – A process attempted to delay the analysis task.
• T1573 – Establishes an encrypted HTTPS connection
• T1010 – Tries to detect debugger
• T1012 – Tries to detect virtual machine
• T1016 – Queries a host’s domain name
• T1027.002 – Obfuscates control flow
• T1047 – Collects BIOS properties
• T1047 – Queries OS version via WMI
• T1047 – Collects hardware properties
• T1047 – Tries to detect the presence of antivirus software
• T1057 – Enumerates running processes
• T1082 – Collects BIOS properties
• T1082 – Enumerates running processes
• T1082 – Queries OS version via WMI
• T1082 – Collects hardware properties
• T1106 – Tries to evade debugger
• T1124 – Tries to detect virtual machine
• T1497.001 – Tries to detect virtual machine
• T1497.003 – Delays execution
• T1497.003 – Tries to detect virtual machine
• T1518.001 – Tries to detect the presence of antivirus software
• T1562.001 – Modifies native system functions
• T1622 – Tries to detect debugger
• T1622 – Tries to evade debugger
• 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
• 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
• 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)
• T1055 – May try to detect the Windows Explorer process (often used for injection)
• T1497 – Checks if the current process is being debugged
• T1497 – May sleep (evasive loops) to hinder dynamic analysis
• T1497 – Hides threads from debuggers
• T1497 – Contains capabilities to detect virtual machines
• T1497 – Checks for debuggers (devices)
• T1497 – Checks for debuggers (window names)
• 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
• T1518.001 – Tries to detect sandboxes / dynamic malware analysis system (registry check)
• T1518.001 – Checks if the current process is being debugged
• T1518.001 – Tries to detect virtualization through RDTSC time measurements
• T1518.001 – Hides threads from debuggers
• T1518.001 – Tries to evade debugger and weak emulator (self modifying code)
• T1518.001 – Contains capabilities to detect virtual machines
• T1518.001 – Checks for debuggers (devices)
• T1518.001 – Checks for debuggers (window names)
• T1057 – Queries a list of all running processes
• T1057 – May try to detect the Windows Explorer process (often used for injection)
• T1082 – Tries to detect virtualization through RDTSC time measurements
• T1082 – Tries to evade debugger and weak emulator (self modifying code)
• T1573 – Uses HTTPS
• T1071 – Uses HTTPS

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.