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 56+ minutes, this malware was rapidly detected — demonstrating excellent security controls that intercepted the threat during initial execution phases, severely limiting adversary capabilities.

Global Detection Posture — Who Caught It, Who Missed It

VirusTotal engines: 72. Detected as malicious: 45. Missed: 27. Coverage: 62.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

Intensive file system activity (70.47% of behavior) indicates data harvesting, file encryption, or dropper behavior. The threat is actively searching for and manipulating files across the system.

MITRE ATT&CK Mapping

• T1129 – parse PE header
• T1082 – get disk information
• T1083 – enumerate files on Windows
• T1057 – enumerate process modules
• T1083 – enumerate files recursively
• T1129 – link many functions at runtime
• T1497.001 – reference anti-VM strings targeting Xen
• T1082 – query environment variable
• T1083 – get file size
• T1059 – accept command line arguments
• T1083 – get common file path
• T1027 – encode data using XOR
• T1129 – link function at runtime on Windows
• T1129 – Drops a binary and executes it
• T1202 – Uses Windows utilities for basic functionality
• T1202 – Uses suspicious command line tools or Windows utilities
• T1562 – Attempts to modify Microsoft Office security settings
• T1055 – Creates a process in a suspended state, likely for injection
• T1112 – Attempts to modify Microsoft Office security settings
• T1112 – Installs itself for autorun at Windows startup
• T1562.001 – Attempts to modify Microsoft Office security settings
• T1027 – The binary contains an unknown PE section name indicative of packing
• T1221 – A document file initiated network communications indicative of a potential exploit or payload download
• T1027.002 – The binary contains an unknown PE section name indicative of packing
• 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
• T1082 – Checks available memory
• T1071 – Reads data out of its own binary image
• T1071 – Accesses the UserInfo registry key, potentially used for discovery
• T1071 – A document file initiated network communications indicative of a potential exploit or payload download
• T1071 – A potential decoy document was displayed to the user
• T1071 – Attempts to connect to a dead IP:Port
• T1071 – The PE file contains an overlay
• T1573 – Establishes an encrypted HTTPS connection
• T1486 – Exhibits possible ransomware or wiper file modification behavior: overwrites_existing_files
• T1485 – Anomalous file deletion behavior detected (10+)
• T1070.006 – Binary contains a suspicious time stamp
• T1083 – Reads ini files
• T1082 – Queries the volume information (name, serial number etc) of a device
• 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.