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: 72. Detected as malicious: 42. Missed: 30. Coverage: 58.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.

MITRE ATT&CK Mapping

• T1083 – get common file path
• T1027 – encrypt data using RC4 PRGA
• T1027 – encrypt data using Salsa20 or ChaCha
• T1059 – accept command line arguments
• T1027 – reference Base64 string
• T1562.001 – disable Windows Defender features via registry on Windows
• T1129 – link function at runtime on Windows
• T1027 – encode data using Base64
• T1083 – check if file exists
• T1027 – encode data using XOR
• T1129 – parse PE header
• T1082 – query environment variable
• T1129 – link many functions at runtime
• T1027 – encrypt data using speck
• T1202 – Uses suspicious command line tools or Windows utilities
• T1202 – Uses Windows utilities for basic functionality
• T1055 – Creates a process in a suspended state, likely for injection
• T1082 – Checks available memory
• T1057 – Uses Windows utilities to enumerate running processes
• T1106 – Guard pages use detected – possible anti-debugging.
• T1059 – Executed a command line with /C or /R argument to terminate command shell on completion which can be used to hide execution
• T1562.001 – Creates guard pages, often used to prevent reverse engineering and debugging
• T1070.004 – May delete shadow drive data (may be related to ransomware)
• T1090 – Found Tor onion address

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.