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 7+ hours, this malware remained undetected — a several-hour window that allowed the adversary to complete initial compromise and begin early-stage persistence establishment.

Global Detection Posture — Who Caught It, Who Missed It

VirusTotal engines: 73. Detected as malicious: 56. Missed: 17. Coverage: 76.7%.

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

• T1083 – check if file exists
• T1222 – set file attributes
• T1560.002 – compress data using GZip in .NET
• T1083 – check if directory exists
• T1082 – query environment variable
• T1497.001 – reference anti-VM strings targeting Xen
• T1003 – Harvests information related to installed mail clients
• T1003 – Steals private information from local Internet browsers
• T1539 – Touches a file containing cookies, possibly for information gathering
• T1555 – Steals private information from local Internet browsers
• T1552 – Harvests information related to installed mail clients
• T1552 – Steals private information from local Internet browsers
• T1555.003 – Steals private information from local Internet browsers
• T1552.001 – Harvests information related to installed mail clients
• T1552.001 – Steals private information from local Internet browsers
• T1114 – Harvests information related to installed mail clients
• T1005 – Harvests information related to installed mail clients
• T1005 – Steals private information from local Internet browsers
• T1074 – Manipulates data from or to the Recycle Bin
• T1547 – Installs itself for autorun at Windows startup
• T1547.001 – Installs itself for autorun at Windows startup
• T1548 – A file was accessed within the Public folder.
• T1202 – Uses suspicious command line tools or Windows utilities
• T1202 – Uses Windows utilities for basic functionality
• T1036 – A file was accessed within the Public folder.
• T1112 – Installs itself for autorun at Windows startup
• T1064 – A scripting utility was executed
• T1027 – The binary likely contains encrypted or compressed data
• T1027.002 – The binary likely contains encrypted or compressed data
• T1082 – Checks available memory
• T1071 – Yara detections observed in process dumps, payloads or dropped files
• T1071 – Reads data out of its own binary image
• T1071 – A process attempted to delay the analysis task.
• T1106 – Created a process from a suspicious location
• T1106 – Guard pages use detected – possible anti-debugging.
• T1059 – A scripting utility was executed
• T1486 – Performs a large number of encryption calls using the same key possibly indicative of ransomware file encryption behavior
• T1486 – Creates a known WannaCry ransomware decryption instruction / key file.
• T1486 – Exhibits possible ransomware or wiper file modification behavior: mass_file_deletion overwrites_existing_files
• T1485 – Anomalous file deletion behavior detected (10+)
• T1129 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1083 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1027 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1129 – The process attempted to dynamically load a malicious function
• T1059 – Detected command line output monitoring
• T1564.003 – Detected the creation of a hidden window (common execution hiding technique)
• T1140 – Detected an attempt to pull out some data from the binary image
• T1129 – The process tried to load dynamically one or more functions.
• T1129 – Detected a call to NtDelayExecution API: the process may have attempted a sandbox evasion (sleeping!).
• T1083 – Detected a call to NtDelayExecution API: the process may have attempted a sandbox evasion (sleeping!).
• T1027 – Detected a call to NtDelayExecution API: the process may have attempted a sandbox evasion (sleeping!).
• T1057 – The process has tried to detect the debugger probing the use of page guards.
• T1027.009 – The process has executed a dropped binary
• T1057 – The process attempted to detect a running debugger using common APIs
• T1089 – The process has tried to suspend a sandbox-related thread (possible sandbox evasion attempt)
• T1082 – Queries for the computername
• T1081 – Detected an attempt to access Browser data that may contain sensible informations (e.g. user credentials)
• T1119 – Detected an attempt to access Browser data that may contain sensible informations (e.g. user credentials)
• T1158 – Detected the creation of a non white-listed hidden or system file
• T1105 – The process acted as a ransomware (suspicious behaviours common in ransomwares were detected)
• T1107 – The process acted as a ransomware (suspicious behaviours common in ransomwares were detected)
• T1082 – The process tried to collect informations about the system reading some known registry keys
• T1012 – The process tried to collect informations about the system reading some known registry keys
• T1129 – Manalize Local SandBox Strings
• T1083 – Manalize Local SandBox Strings
• T1027 – Manalize Local SandBox Strings
• T1070 – The process attempted to delete web history
• T1107 – The process attempted to delete web history
• T1129 – The process exhibits a know Trojan behaviour (Zeus)
• T1083 – The process exhibits a know Trojan behaviour (Zeus)
• T1027 – The process exhibits a know Trojan behaviour (Zeus)
• T1112 – The process has tried to set its autorun on the system startup
• T1060 – The process has tried to set its autorun on the system startup
• T1050 – The process has tried to set its autorun on the system startup
• T1129 – The process wrote a message on disk that could be related to a ransomware activity
• T1083 – The process wrote a message on disk that could be related to a ransomware activity
• T1027 – The process wrote a message on disk that could be related to a ransomware activity
• T1027.009 – Drops interesting files and uses them
• T1497 – Allocates memory with a write watch (potentially for evading sandboxes)
• T1562.001 – Creates guard pages, often used to prevent reverse engineering and debugging
• T1070.006 – Binary contains a suspicious time stamp
• T1083 – Reads ini files
• T1082 – Queries the volume information (name, serial number etc) of a device
• T1082 – Queries the cryptographic machine GUID
• T1112 – Stores large binary data to the registry
• T1497 – May sleep (evasive loops) to hinder dynamic analysis

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.