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: 55. Missed: 18. Coverage: 75.3%.

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.52% 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 – invoke .NET assembly method
• T1564 – A process created a hidden window
• T1562 – Attempts to modify Windows Defender using PowerShell
• T1055 – Writes to the memory another process
• T1112 – Stores JavaScript or a script command in the registry, likely for fileless persistence
• 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
• T1057 – Enumerates the modules from a process (may be used to locate base addresses in process injection)
• T1071 – At least one IP Address, Domain, or File Name was found in a crypto call
• T1071 – The PE file contains a PDB path
• T1071 – Terminates another process
• T1071 – Reads from the memory of another process
• T1106 – Guard pages use detected – possible anti-debugging.
• T1059 – A scripting utility was executed
• T1059 – Stores JavaScript or a script command in the registry, likely for fileless persistence
• T1059 – Attempts to modify Windows Defender using PowerShell
• T1129 – 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
• T1129 – The process tried to load dynamically one or more functions.
• T1564.003 – Detected the creation of a hidden window (common execution hiding technique)
• T1057 – The process has tried to detect the debugger probing the use of page guards.
• T1129 – 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
• T1086 – 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
• T1129 – A process attempted to delay the analysis task by a long amount of time.
• 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.