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: 54. Missed: 19. Coverage: 74.0%.

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

This threat shows heavy registry manipulation (32.47% of total behavior), indicating persistent backdoor installation, configuration tampering, or system policy modification attempts. The malware likely establishes persistence mechanisms and modifies security settings to maintain long-term access.

MITRE ATT&CK Mapping

• T1222 – set file attributes
• T1547.001 – persist via Run registry key
• T1012 – query or enumerate registry key
• T1560.002 – compress data using GZip in .NET
• T1083 – check if directory exists
• T1082 – query environment variable
• T1083 – check if file exists
• T1129 – Drops a binary and executes it
• T1106 – Guard pages use detected – possible anti-debugging.
• T1106 – Created a process from a suspicious location
• T1059 – Attempts to modify Windows Defender using PowerShell
• T1059 – A scripting utility was executed
• T1059 – Attempts to execute suspicious powershell command arguments
• T1064 – A scripting utility was executed
• T1064 – Attempts to execute suspicious powershell command arguments
• T1059.001 – Attempts to execute suspicious powershell command arguments
• T1564 – A process created a hidden window
• T1562 – Attempts to modify Windows Defender using PowerShell
• T1562 – Tries to unhook or modify Windows functions monitored by CAPE
• T1112 – Installs itself for autorun at Windows startup
• T1562.001 – Attempts to modify Windows Defender using PowerShell
• T1562.001 – Tries to unhook or modify Windows functions monitored by CAPE
• T1027 – The binary likely contains encrypted or compressed data
• T1564.003 – A process created a hidden window
• T1027.002 – The binary likely contains encrypted or compressed data
• T1547 – Installs itself for autorun at Windows startup
• T1547.001 – Installs itself for autorun at Windows startup
• T1082 – Checks available memory
• T1082 – Collects information to fingerprint the system
• T1057 – Enumerates running processes
• T1012 – Collects information to fingerprint the system
• T1071 – Reads data out of its own binary image
• T1071 – Reads from the memory of another process
• T1071 – Yara detections observed in process dumps, payloads or dropped files
• T1071 – At least one IP Address, Domain, or File Name was found in a crypto call
• T1059.001 – Bypasses PowerShell execution policy
• T1547.001 – Creates an autostart registry key
• T1548 – Found direct / indirect Syscall (likely to bypass EDR)
• T1036 – Creates files inside the user directory
• T1562.001 – Creates guard pages, often used to prevent reverse engineering and debugging
• T1562.001 – Adds a directory exclusion to Windows Defender
• T1497 – Checks if the current process is being debugged
• T1497 – Checks for kernel debuggers (NtQuerySystemInformation(SystemKernelDebuggerInformation))
• T1497 – Allocates memory with a write watch (potentially for evading sandboxes)
• T1497 – Queries disk information (often used to detect virtual machines)
• T1497 – Hides threads from debuggers
• T1497 – May sleep (evasive loops) to hinder dynamic analysis
• T1027 – Sample is packed with UPX
• T1027.002 – Sample is packed with UPX
• T1056 – Sample has functionality to log and monitor keystrokes, analyze it with the keystroke simulation cookbook
• T1056 – Installs a raw input device (often for capturing keystrokes)
• T1518.001 – Tries to detect debuggers (CloseHandle check)
• T1518.001 – Checks if the current process is being debugged
• T1518.001 – Checks for kernel debuggers (NtQuerySystemInformation(SystemKernelDebuggerInformation))
• T1518.001 – Queries disk information (often used to detect virtual machines)
• T1518.001 – Hides threads from debuggers
• T1518.001 – Tries to evade analysis by execution special instruction (VM detection)
• T1057 – Queries a list of all running processes
• T1083 – Reads ini files
• T1082 – Queries the cryptographic machine GUID
• T1082 – Queries disk information (often used to detect virtual machines)
• T1082 – Queries the volume information (name, serial number etc) of a device
• T1082 – Tries to evade analysis by execution special instruction (VM detection)
• T1005 – Found many strings related to Crypto-Wallets (likely being stolen)

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.