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: 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 (56.04% 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

• T1202 – Uses Windows utilities for basic functionality
• T1202 – Uses suspicious command line tools or Windows utilities
• T1112 – Stores JavaScript or a script command in the registry, likely for fileless persistence
• T1070 – Deletes executed files from disk
• T1064 – A scripting utility was executed
• T1064 – Attempts to execute suspicious powershell command arguments
• T1497 – Detects VirtualBox through the presence of a registry key
• T1497 – Checks the version of Bios, possibly for anti-virtualization
• T1027 – The binary likely contains encrypted or compressed data
• T1027 – The binary contains an unknown PE section name indicative of packing
• T1027.002 – The binary likely contains encrypted or compressed data
• T1027.002 – The binary contains an unknown PE section name indicative of packing
• 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 – Checks for the presence of known devices 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 – Expresses interest in specific running processes
• 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 – Detects VirtualBox through the presence of a registry key
• 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 – HTTP traffic contains suspicious features which may be indicative of malware related traffic
• T1071 – Executable is attempted to be downloaded from an IP
• T1071 – Resolves a suspicious Top Level Domain (TLD)
• T1071 – Yara detections observed in process dumps, payloads or dropped files
• T1071 – Makes a suspicious HTTP request to a commonly exploitable directory with questionable file ext
• T1573 – Establishes an encrypted HTTPS connection
• T1106 – Guard pages use detected – possible anti-debugging.
• T1059 – Stores JavaScript or a script command in the registry, likely for fileless persistence
• T1059 – A scripting utility was executed
• T1059 – Attempts to execute suspicious powershell command arguments
• T1059.001 – Attempts to execute suspicious powershell command arguments
• T1010 – Tries to detect debugger
• T1012 – Tries to detect virtual machine
• T1027.002 – Obfuscates control flow
• T1057 – Enumerates running processes
• T1106 – Tries to evade debugger
• T1124 – Tries to detect virtual machine
• T1497.001 – Tries to detect virtual machine
• T1497.003 – Tries to detect virtual machine
• T1562.001 – Modifies native system functions
• T1622 – Tries to detect debugger
• T1622 – Tries to evade debugger
• 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
• 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)
• T1047 – Queries BIOS Information (via WMI, Win32_Bios)
• T1055 – May try to detect the Windows Explorer process (often used for injection)
• T1497 – Checks if the current process is being debugged
• T1497 – Checks for debuggers (window names)
• T1497 – Checks for debuggers (devices)
• T1497 – Contains capabilities to detect virtual machines
• T1497 – Hides threads from debuggers
• T1497 – May sleep (evasive loops) to hinder dynamic analysis
• T1027 – Binary may include packed or crypted data
• T1027.002 – Binary may include packed or crypted data
• T1027.002 – PE file has section (not .text) which is very likely to contain packed code (zlib compression ratio < 0.011)
• T1518.001 – Checks if the current process is being debugged
• T1518.001 – Checks for debuggers (window names)
• T1518.001 – Checks for debuggers (devices)
• T1518.001 – Tries to evade debugger and weak emulator (self modifying code)
• T1518.001 – Contains capabilities to detect virtual machines
• T1518.001 – Tries to detect virtualization through RDTSC time measurements
• T1518.001 – Hides threads from debuggers
• T1518.001 – Tries to detect sandboxes / dynamic malware analysis system (registry check)
• T1057 – May try to detect the Windows Explorer process (often used for injection)
• T1057 – Queries a list of all running processes
• T1082 – Tries to evade debugger and weak emulator (self modifying code)
• T1082 – Tries to detect virtualization through RDTSC time measurements
• T1082 – Queries a list of all running drivers
• T1082 – Queries the volume information (name, serial number etc) of a device
• T1082 – Queries the cryptographic machine GUID
• T1082 – Queries BIOS Information (via WMI, Win32_Bios)
• T1005 – Tries to steal Crypto Currency Wallets
• T1005 – Found many strings related to Crypto-Wallets (likely being stolen)
• T1573 – Uses HTTPS
• T1105 – Downloads files from webservers via HTTP
• T1095 – Downloads files from webservers via HTTP
• T1071 – Uses HTTPS
• T1071 – Downloads files from webservers via HTTP

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.