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: 50. Missed: 23. Coverage: 68.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

Dominant system-level operations (60.76% 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

• T1082 – query environment variable
• T1012 – query or enumerate registry value
• T1134 – modify access privileges
• T1082 – get system information on Windows
• T1082 – get memory capacity
• T1129 – parse PE header
• T1129 – link function at runtime on Windows
• T1027 – encode data using XOR
• T1027 – decode data using Base64 via dword translation table
• T1027 – encrypt data using RC4 KSA
• T1129 – link many functions at runtime
• T1129 – access PEB ldr_data
• T1082 – get number of processors
• T1614 – get geographical location
• T1055 – Writes to the memory another process
• T1055 – Writes an executable to the memory of another process
• 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 available memory
• T1057 – Enumerates the modules from a process (may be used to locate base addresses in process injection)
• T1071 – Yara detections observed in process dumps, payloads or dropped files
• T1005 – Searches for sensitive browser data
• T1005 – Reads sensitive browser data
• T1012 – Query OS Information
• T1012 – Possibly does reconnaissance
• T1027.002 – Creates a page with write and execute permissions
• T1055 – Writes into the memory of another process
• T1055 – Modifies control flow of another process
• T1055.012 – Process Hollowing
• T1057 – Enumerates running processes
• T1071.004 – Performs DNS request
• T1082 – Enumerates running processes
• T1082 – Query OS Information
• T1083 – Searches for sensitive browser data
• T1083 – Possibly does reconnaissance
• T1095 – Connects to remote host
• T1106 – Tries to detect kernel debugger
• T1115 – Captures clipboard data
• T1119 – Searches for sensitive browser data
• T1119 – Reads sensitive browser data
• T1497.003 – Delays execution
• T1552.001 – Searches for sensitive browser data
• T1555.003 – Reads sensitive browser data
• T1564.003 – Creates process with hidden window
• T1622 – Tries to detect kernel debugger
• T1622 – Tries to detect debugger
• T1059 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1129 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1033 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1012 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1134 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1518 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1057 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1134.004 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1082 – 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.
• T1083 – SetUnhandledExceptionFilter detected: superseding the top-level exception handler of each thread of a process is a common anti-debug technique.
• T1129 – The process tried to load dynamically one or more functions.
• T1045 – Manalize Local SandBox Packer Harvesting
• T1057 – The process attempted to detect a running debugger using common APIs
• T1059 – Manalize Local SandBox Find Crypto
• T1129 – Manalize Local SandBox Find Crypto
• T1033 – Manalize Local SandBox Find Crypto
• T1012 – Manalize Local SandBox Find Crypto
• T1134 – Manalize Local SandBox Find Crypto
• T1518 – Manalize Local SandBox Find Crypto
• T1057 – Manalize Local SandBox Find Crypto
• T1134.004 – Manalize Local SandBox Find Crypto
• T1082 – Manalize Local SandBox Find Crypto
• T1027 – Manalize Local SandBox Find Crypto
• T1083 – Manalize Local SandBox Find Crypto
• T1059 – Manalize Local SandBox Strings
• T1129 – Manalize Local SandBox Strings
• T1033 – Manalize Local SandBox Strings
• T1012 – Manalize Local SandBox Strings
• T1134 – Manalize Local SandBox Strings
• T1518 – Manalize Local SandBox Strings
• T1057 – Manalize Local SandBox Strings
• T1134.004 – Manalize Local SandBox Strings
• T1082 – Manalize Local SandBox Strings
• T1027 – Manalize Local SandBox Strings
• T1083 – Manalize Local SandBox Strings
• T1063 – It Tries to detect injection methods
• T1542.003 – May use bcdedit to modify the Windows boot settings
• T1055 – Allocates memory in foreign processes
• T1055 – Modifies the context of a thread in another process (thread injection)
• T1055 – Injects a PE file into a foreign processes
• T1055 – Maps a DLL or memory area into another process
• T1055 – Writes to foreign memory regions
• T1055 – Queues an APC in another process (thread injection)
• T1055 – May try to detect the Windows Explorer process (often used for injection)
• T1562.001 – Launches processes in debugging mode, may be used to hinder debugging
• T1497 – Allocates memory with a write watch (potentially for evading sandboxes)
• T1497 – May sleep (evasive loops) to hinder dynamic analysis
• T1497 – Checks if the current process is being debugged
• T1003 – Tries to harvest and steal browser information (history, passwords, etc)
• T1518.001 – Switches to a customs stack to bypass stack traces
• T1518.001 – Checks if the current process is being debugged
• T1057 – Queries a list of all running processes
• T1057 – May try to detect the Windows Explorer process (often used for injection)
• T1082 – Checks if Microsoft Office is installed
• T1082 – Switches to a customs stack to bypass stack traces
• T1114 – Tries to search for mail accounts
• T1005 – Tries to harvest and steal browser information (history, passwords, etc)
• T1105 – Downloads files from webservers via HTTP
• T1095 – Downloads files from webservers via HTTP
• 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.