Trojan Downloader (Upatre) Writes Temp EXE and Beacons for Payloads


Zero‑Dwell Threat Intelligence Report

A narrative, executive‑ready view into the malware’s behavior, exposure, and reliable defenses.
Generated: 2025-11-12 22:17:10 UTC

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.

File
hasfj.exe
Type
PE32 executable (GUI) Intel 80386, for MS Windows
SHA‑1
b7f9bdf3d643cd8dbffd4882e9dc2256406f0a3d
MD5
93d637d4f71975db55806c7908feca96
First Seen
2025-10-06 05:57:33.074844
Last Analysis
2025-10-06 07:50:35.467679
Dwell Time
0 days, 7 hours, 33 minutes

Extended Dwell Time Impact

For 1+ hours, this malware remained undetected — a limited but sufficient window for the adversary to complete initial execution and establish basic system access.

Comparative Context

Industry studies report a median dwell time closer to 21–24 days. This case represents rapid detection and containment within hours rather than days.

Timeline

Time (UTC) Event Elapsed
2025-10-06 02:23:37 UTC First VirusTotal submission
2025-10-08 14:28:08 UTC Latest analysis snapshot 2 days, 12 hours, 4 minutes
2025-11-12 22:17:10 UTC Report generation time 30 days, 4 hours, 53 minutes

Why It Matters

Every additional day of dwell time is not just an abstract number — it is attacker opportunity. Each day equates to more time for lateral movement, stealth persistence, and intelligence gathering.

Global Detection Posture — Who Caught It, Who Missed It

VirusTotal engines: 73. Detected as malicious: 66. Missed: 7. Coverage: 90.4%.

Detected Vendors

  • Xcitium
  • +65 additional vendors (names not provided)

List includes Xcitium plus an additional 65 vendors per the provided summary.

Missed Vendors

  • CMC
  • MaxSecure
  • SUPERAntiSpyware
  • TACHYON
  • tehtris
  • TrendMicro
  • Yandex

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 (40.48% 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.

Behavior Categories (weighted)

Weight values represent the frequency and intensity of malware interactions with specific system components. Higher weights indicate more aggressive targeting of that category. Each operation (registry access, file modification, network connection, etc.) contributes to the category’s total weight, providing a quantitative measure of the malware’s behavioral focus.

Category Weight Percentage
System 272 40.48%
Registry 266 39.58%
File System 45 6.70%
Process 36 5.36%
Device 22 3.27%
Windows 13 1.93%
Synchronization 8 1.19%
Com 6 0.89%
Misc 4 0.60%

MITRE ATT&CK Mapping

  • T1027 – encrypt data using RC4 PRGA
  • T1564.003 – hide graphical window
  • T1059 – accept command line arguments
  • T1547.001 – reference startup folder

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.

Contacted Domains

Domain IP Country ASN/Org
www.aieov.com 76.223.54.146 United States Amazon.com, Inc.

Observed IPs

IP Country ASN/Org
224.0.0.252
8.8.4.4 United States Google LLC
8.8.8.8 United States Google LLC

DNS Queries

Request Type
5isohu.com A
www.aieov.com A

Contacted IPs

IP Country ASN/Org
224.0.0.252
8.8.4.4 United States Google LLC
8.8.8.8 United States Google LLC

Port Distribution

Port Count Protocols
137 1 udp
5355 4 udp
53 28 udp

UDP Packets

Source IP Dest IP Sport Dport Time Proto
192.168.56.14 192.168.56.255 137 137 3.0821831226348877 udp
192.168.56.14 224.0.0.252 51209 5355 3.0099120140075684 udp
192.168.56.14 224.0.0.252 53401 5355 4.31110692024231 udp
192.168.56.14 224.0.0.252 55094 5355 5.564968109130859 udp
192.168.56.14 224.0.0.252 55848 5355 3.010068893432617 udp
192.168.56.14 8.8.4.4 49916 53 99.04685997962952 udp
192.168.56.14 8.8.4.4 50180 53 146.17210292816162 udp
192.168.56.14 8.8.4.4 50710 53 66.07790398597717 udp
192.168.56.14 8.8.4.4 52815 53 7.141175031661987 udp
192.168.56.14 8.8.4.4 54579 53 51.67239499092102 udp
192.168.56.14 8.8.4.4 54683 53 193.31256008148193 udp
192.168.56.14 8.8.4.4 55914 53 127.85929107666016 udp
192.168.56.14 8.8.4.4 56399 53 175.00012803077698 udp
192.168.56.14 8.8.4.4 60117 53 80.53110194206238 udp
192.168.56.14 8.8.4.4 62022 53 160.5470130443573 udp
192.168.56.14 8.8.4.4 62112 53 36.96906590461731 udp
192.168.56.14 8.8.4.4 63205 53 207.70366501808167 udp
192.168.56.14 8.8.4.4 64753 53 113.43759894371033 udp
192.168.56.14 8.8.4.4 65148 53 22.57833504676819 udp
192.168.56.14 8.8.8.8 49916 53 98.04763793945312 udp
192.168.56.14 8.8.8.8 50180 53 145.17270612716675 udp
192.168.56.14 8.8.8.8 50710 53 65.07811212539673 udp
192.168.56.14 8.8.8.8 52815 53 8.140522956848145 udp
192.168.56.14 8.8.8.8 54579 53 50.672800064086914 udp
192.168.56.14 8.8.8.8 54683 53 192.31247210502625 udp
192.168.56.14 8.8.8.8 55914 53 126.8597640991211 udp
192.168.56.14 8.8.8.8 56399 53 174.00073504447937 udp
192.168.56.14 8.8.8.8 60117 53 79.53154397010803 udp
192.168.56.14 8.8.8.8 62022 53 159.54702711105347 udp
192.168.56.14 8.8.8.8 62112 53 35.977133989334106 udp
192.168.56.14 8.8.8.8 63205 53 206.70427012443542 udp
192.168.56.14 8.8.8.8 64753 53 112.43884706497192 udp
192.168.56.14 8.8.8.8 65148 53 21.578402042388916 udp

Hunting tip: alert on unknown binaries initiating TLS to IP‑lookup services or unusual CDN endpoints — especially early in execution.

What To Do Now — Practical Defense Playbook

  • Contain unknowns: block first‑run binaries by default — signatures catch up, containment works now.
  • EDR controls: alert on keyboard hooks, screen capture APIs, VM/sandbox checks, and command‑shell launches.
  • Registry watch: flag queries/sets under policy paths (e.g., …\FipsAlgorithmPolicy\*).
  • Network rules: inspect outbound TLS to IP‑lookup services and unexpected CDN endpoints.
  • Hunt broadly: sweep endpoints for the indicators above and quarantine positives immediately.

Dwell time equals attacker opportunity. Reducing execution privileges and egress shrinks that window even when vendors disagree.

Scroll to Top