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 1+ 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: 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.44% 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

• T1071 – HTTP traffic contains suspicious features which may be indicative of malware related traffic
• T1027 – The binary contains an unknown PE section name indicative of packing
• T1027.002 – The binary contains an unknown PE section name indicative of packing
• T1016 – Queries a host’s domain name
• T1027.002 – Resolves API functions dynamically
• T1095 – Connects to remote host
• T1095 – Sets up server that accepts incoming connections
• T1497.001 – Tries to detect application sandbox
• T1497.003 – Delays execution
• T1622 – Tries to detect debugger
• T1129 – The process attempted to dynamically load a malicious function
• T1129 – The process tried to load dynamically one or more functions.
• T1140 – Detected an attempt to pull out some data from the binary image
• T1045 – Manalize Local SandBox Packer Harvesting
• 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
• T1071 – Some process has originated direct HTTPS traffic with one or more hosts.
• T1497 – May sleep (evasive loops) to hinder dynamic analysis
• T1082 – Sample reads itself and does not show any behavior, likely it performs some host environment checks and compares to an embedded key
• T1082 – Queries the volume information (name, serial number etc) of a device
• T1573 – Uses HTTPS
• T1095 – Downloads files from webservers via HTTP
• T1095 – Posts data to webserver
• T1095 – Downloads compressed data via HTTP
• T1071 – Downloads files from webservers via HTTP
• T1071 – Posts data to webserver
• T1071 – Uses HTTPS
• T1071 – Downloads compressed data via HTTP
• T1071 – Uses a known web browser user agent for HTTP communication
• T1105 – Downloads files from webservers via HTTP
• T1105 – Downloads compressed data 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.