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 7+ hours, this malware remained undetected — a several-hour window that allowed the adversary to complete initial compromise and begin early-stage persistence establishment.

Global Detection Posture — Who Caught It, Who Missed It

VirusTotal engines: 72. Detected as malicious: 67. Missed: 5. Coverage: 93.1%.

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

• T1543.003 – start service
• T1129 – link function at runtime on Windows
• T1129 – parse PE header
• T1083 – check if file exists
• T1027 – reference AES constants
• T1027 – encode data using XOR
• T1027 – encrypt data using RC4 KSA
• T1012 – query or enumerate registry value
• T1129 – link many functions at runtime
• T1222 – set file attributes
• T1543.003 – persist via Windows service
• T1569.002 – persist via Windows service
• T1082 – get hostname
• T1543.003 – create service
• T1569.002 – create service
• T1083 – get common file path
• T1027 – encrypt data using AES
• T1083 – get file size

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.