Trojan.Downloader.Upatre Deploys CryptoLocker Encryption Module


Zero‑Dwell Threat Intelligence Report

A narrative, executive‑ready view into the malware’s behavior, exposure, and reliable defenses.
Generated: 2025-11-12 07:16:45 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
ujmu19.exe
Type
PE32 executable (GUI) Intel 80386, for MS Windows, UPX compressed
SHA‑1
f3c433f0ba3a8c803572e7bc594273816772fcd3
MD5
c8ac52aa7018cd5bdc167478052bb1eb
First Seen
2025-10-06 08:40:56.783882
Last Analysis
2025-10-06 13:37:18.223354
Dwell Time
0 days, 7 hours, 33 minutes

Extended Dwell Time Impact

For 4+ 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 04:50:19 UTC First VirusTotal submission
2025-10-08 14:09:41 UTC Latest analysis snapshot 2 days, 9 hours, 19 minutes
2025-11-12 07:16:45 UTC Report generation time 30 days, 2 hours, 26 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: 70. Detected as malicious: 64. Missed: 6. Coverage: 91.4%.

Detected Vendors

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

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

Missed Vendors

  • CMC
  • MaxSecure
  • Paloalto
  • TACHYON
  • Yandex
  • Zoner

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 (56.19% 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 254 56.19%
Registry 92 20.35%
File System 37 8.19%
Process 36 7.96%
Device 18 3.98%
Windows 9 1.99%
Com 6 1.33%

MITRE ATT&CK Mapping

  • T1497.001 – reference anti-VM strings
  • T1027.002 – packed with UPX
  • T1027.002 – packed with generic packer

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 27 udp

UDP Packets

Source IP Dest IP Sport Dport Time Proto
192.168.56.14 192.168.56.255 137 137 3.0817148685455322 udp
192.168.56.14 224.0.0.252 51209 5355 3.0108749866485596 udp
192.168.56.14 224.0.0.252 53401 5355 5.156669855117798 udp
192.168.56.14 224.0.0.252 55094 5355 5.563416004180908 udp
192.168.56.14 224.0.0.252 55848 5355 3.012270927429199 udp
192.168.56.14 8.8.4.4 49916 53 99.86000990867615 udp
192.168.56.14 8.8.4.4 50180 53 147.2655529975891 udp
192.168.56.14 8.8.4.4 50710 53 66.90716505050659 udp
192.168.56.14 8.8.4.4 52815 53 8.031800031661987 udp
192.168.56.14 8.8.4.4 54579 53 52.51652789115906 udp
192.168.56.14 8.8.4.4 54683 53 194.4849100112915 udp
192.168.56.14 8.8.4.4 55914 53 128.68781995773315 udp
192.168.56.14 8.8.4.4 56399 53 176.10989904403687 udp
192.168.56.14 8.8.4.4 60117 53 81.3442029953003 udp
192.168.56.14 8.8.4.4 62022 53 161.62561893463135 udp
192.168.56.14 8.8.4.4 62112 53 37.86009502410889 udp
192.168.56.14 8.8.4.4 64753 53 114.25081300735474 udp
192.168.56.14 8.8.4.4 65148 53 23.484544038772583 udp
192.168.56.14 8.8.8.8 49916 53 98.85984587669373 udp
192.168.56.14 8.8.8.8 50180 53 146.26650881767273 udp
192.168.56.14 8.8.8.8 50710 53 65.90677094459534 udp
192.168.56.14 8.8.8.8 52815 53 9.031441926956177 udp
192.168.56.14 8.8.8.8 54579 53 51.516185998916626 udp
192.168.56.14 8.8.8.8 54683 53 193.48533082008362 udp
192.168.56.14 8.8.8.8 55914 53 127.68879985809326 udp
192.168.56.14 8.8.8.8 56399 53 175.1097228527069 udp
192.168.56.14 8.8.8.8 60117 53 80.3440408706665 udp
192.168.56.14 8.8.8.8 62022 53 160.6258099079132 udp
192.168.56.14 8.8.8.8 62112 53 36.860997915267944 udp
192.168.56.14 8.8.8.8 63205 53 207.8759160041809 udp
192.168.56.14 8.8.8.8 64753 53 113.25738883018494 udp
192.168.56.14 8.8.8.8 65148 53 22.485435009002686 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