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 17+ hours, this malware remained undetected — a half-day window that permitted the adversary to complete initial execution, establish basic persistence, and perform initial system enumeration.

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

This threat shows heavy registry manipulation (41.25% 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

• T1620 – load .NET assembly
• 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
• T1539 – Touches a file containing cookies, possibly for information gathering
• T1082 – Checks available memory
• T1071 – Yara detections observed in process dumps, payloads or dropped files
• T1106 – Guard pages use detected – possible anti-debugging.
• T1059 – Attempts to modify Windows Defender using PowerShell
• T1059 – A scripting utility was executed
• T1129 – The process attempted to dynamically load a malicious function
• T1059 – Detected command line output monitoring
• T1057 – The process has tried to detect the debugger probing the use of page guards.
• T1129 – The process tried to load dynamically one or more functions.
• T1564.003 – Detected the creation of a hidden window (common execution hiding technique)
• T1086 – Detected the execution of a powershell command with one or more suspicious parameter
• T1027 – 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

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.