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: 47. Missed: 26. Coverage: 64.4%.

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

• T1082 – get system information on Windows
• T1129 – link many functions at runtime
• T1134 – modify access privileges
• T1082 – get memory capacity
• T1129 – access PEB ldr_data
• T1082 – get number of processors
• T1614 – get geographical location
• T1082 – query environment variable
• T1129 – link function at runtime on Windows
• T1027 – reference Base64 string
• T1033 – Collects and encrypts information about the computer likely to send to C2 server
• T1082 – Checks available memory
• T1057 – Enumerates the modules from a process (may be used to locate base addresses in process injection)
• T1547 – Installs itself for autorun at Windows startup
• T1547.001 – Installs itself for autorun at Windows startup
• T1055 – Writes an executable to the memory of another process
• T1055 – Writes to the memory another process
• T1112 – Installs itself for autorun at Windows startup
• 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
• T1071 – The PE file contains an overlay
• T1071 – Reads from the memory of another process
• T1071 – At least one IP Address, Domain, or File Name was found in a crypto call
• T1071 – Yara detections observed in process dumps, payloads or dropped files
• T1071 – Attempts to connect to a dead IP:Port
• T1106 – Guard pages use detected – possible anti-debugging.
• T1005 – Attempts to access Bitcoin/ALTCoin wallets
• T1560 – Collects and encrypts information about the computer likely to send to C2 server
• T1129 – The process tried to load dynamically one or more functions.
• T1045 – Manalize Local SandBox Packer Harvesting
• T1063 – It Tries to detect injection methods
• T1036 – Drops files with a non matching file extension (content does not match to file extension)
• T1036 – Creates files inside the user directory
• T1036 – Drops PE files with benign system names
• T1036 – Drops PE files with a suspicious file extension
• T1218.011 – Runs a DLL by calling functions
• T1497 – May sleep (evasive loops) to hinder dynamic analysis
• T1070.006 – Binary contains a suspicious time stamp
• T1040 – NDIS Filter Driver detected (used to intercept and sniff network traffic)

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.