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

• T1083 – check if file exists
• T1620 – invoke .NET assembly method
• T1003 – Harvests credentials from local FTP client softwares
• T1003 – Harvests information related to installed mail clients
• T1003 – Harvests information related to installed instant messenger clients
• T1539 – Touches a file containing cookies, possibly for information gathering
• T1552 – Harvests credentials from local FTP client softwares
• T1552 – Harvests information related to installed mail clients
• T1552 – Harvests information related to installed instant messenger clients
• T1552.001 – Harvests credentials from local FTP client softwares
• T1552.001 – Harvests information related to installed mail clients
• T1552.001 – Harvests information related to installed instant messenger clients
• T1564 – A process created a hidden window
• T1562 – Attempts to modify Windows Defender using PowerShell
• T1055 – Writes an executable to the memory of another process
• T1055 – Writes to the memory another process
• T1064 – A scripting utility was executed
• T1562.001 – Attempts to modify Windows Defender using PowerShell
• 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
• T1114 – Harvests information related to installed mail clients
• T1005 – Harvests credentials from local FTP client softwares
• T1005 – Harvests information related to installed mail clients
• T1005 – Harvests information related to installed instant messenger clients
• T1082 – Checks available memory
• T1083 – Attempts to identify installed AV products by installation directory
• T1518.001 – Attempts to identify installed AV products by installation directory
• T1518 – Attempts to identify installed AV products by installation directory
• T1071 – Reads from the memory of another process
• T1071 – Looks up the external IP address
• T1071 – A process attempted to delay the analysis task by a long amount of time.
• 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
• T1568 – Connects to a Dynamic DNS Domain
• T1573 – Establishes an encrypted HTTPS connection to a social media API
• T1573 – Establishes an encrypted HTTPS connection
• T1106 – Guard pages use detected – possible anti-debugging.
• T1059 – A scripting utility was executed
• T1059 – Attempts to modify Windows Defender using PowerShell
• 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)
• T1129 – The process tried to load dynamically one or more functions.
• T1057 – The process has tried to detect the debugger probing the use of page guards.
• T1027 – Detected the execution of a powershell command with one or more suspicious parameter
• T1086 – Detected the execution of a powershell command with one or more suspicious parameter
• T1129 – Detected the execution of a powershell command with one or more suspicious parameter
• 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
• T1086 – Detected some PowerShell commands executions
• T1027.009 – Drops interesting files and uses them
• T1055 – Injects a PE file into a foreign processes
• 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 – May sleep (evasive loops) to hinder dynamic analysis
• T1497 – Allocates memory with a write watch (potentially for evading sandboxes)
• T1027 – Binary may include packed or crypted data
• T1027.002 – PE file has an executable .text section which is very likely to contain packed code (zlib compression ratio < 0.3)
• T1027.002 – Binary may include packed or crypted data
• T1003 – Tries to harvest and steal browser information (history, passwords, etc)
• T1057 – Queries a list of all running processes
• T1016 – Checks the online ip address of the machine
• T1083 – Reads ini files
• T1082 – Queries the volume information (name, serial number etc) of a device
• T1082 – Queries the cryptographic machine GUID
• T1082 – Checks if Microsoft Office is installed
• T1114 – Tries to search for mail accounts
• T1005 – Tries to harvest and steal browser information (history, passwords, etc)
• T1102 – Connects to a pastebin service (like for C&C)
• T1573 – Uses HTTPS
• T1105 – Downloads files from webservers via HTTP
• T1095 – Downloads files from webservers via HTTP
• T1071 – Uses HTTPS
• T1071 – Downloads files from webservers via HTTP
• T1071 – Uses a known web browser user agent for HTTP communication

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.