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 5+ days, this malware remained undetected — an unusually long window that granted the adversary the ability to persist, recon, and potentially exfiltrate data with zero alerts.

Global Detection Posture — Who Caught It, Who Missed It

VirusTotal engines: 77. Detected as malicious: 57. Missed: 15. 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

This threat blends evasive checks with data collection and outbound communications. Behavior tags point to sandbox detection, prolonged sleeps, registry reconnaissance, and encrypted egress — a classic quiet‑then‑talk pattern.

MITRE ATT&CK Mapping

• T1497 – Virtualization/Sandbox Evasion (checks BIOS/WMI; long sleeps)
• T1113 – Screen Capture (WinAPI)
• T1056.001 – Input Capture: Keylogging (global keyboard hook)
• T1012 – Query Registry (policy & crypto OID keys)
• T1071.001 – Web Protocols (HTTPS to external IP lookup service)
• T1105 – Ingress Tool Transfer / C2 data (socket/HTTP usage)

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.