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: 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

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

• T1546.001 – persist via default file association registry key
• T1112 – delete registry value
• T1055.003 – inject thread
• T1620 – inject thread
• T1057 – enumerate processes
• T1518 – enumerate processes
• T1129 – parse PE header
• T1539 – Touches a file containing cookies, possibly for information gathering
• T1071 – At least one IP Address, Domain, or File Name was found in a crypto call
• T1071 – Attempts to connect to a dead IP:Port
• T1071 – Performs HTTP requests potentially not found in PCAP.
• T1071 – Yara detections observed in process dumps, payloads or dropped files
• T1071 – Terminates another process
• T1071 – Reads from the memory of another process
• T1071 – Resolves a suspicious Top Level Domain (TLD)
• T1573 – Establishes an encrypted HTTPS connection to a social media API
• T1573 – Establishes an encrypted HTTPS connection
• T1573 – Establishes an encrypted HTTPS connection to an open-source code-hosting platform
• T1106 – Guard pages use detected – possible anti-debugging.
• T1036 – A file was accessed within the Public folder.
• T1055 – Contains .tls (Thread Local Storage) section
• T1548 – A file was accessed within the Public folder.
• T1497 – Checks for mouse movement
• T1057 – Expresses interest in specific running processes
• T1057 – Enumerates running processes
• T1129 – The process attempted to dynamically load a malicious function
• T1129 – The process tried to load dynamically one or more functions.
• T1045 – Manalize Local SandBox Packer Harvesting
• T1071 – Detected HTTP requests to some non white-listed domains
• T1082 – Queries for the computername
• T1185 – Detected an attempt to write registry keys related to the proxy settings
• T1112 – Detected an attempt to write registry keys related to the proxy settings
• T1071 – Some process has originated direct HTTPS traffic with one or more hosts.
• T1053 – It registers tasks through ITaskFolder::RegisterTaskDefinition
• T1053 – Creates COM task schedule object (often to register a task for autostart)
• T1036 – Creates files inside the user directory
• T1057 – Queries a list of all running processes
• T1573 – Uses HTTPS
• T1071 – Uses HTTPS

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.