Massive PE Resource Payload Exhibiting Classic Worm Capabilities


Zero‑Dwell Threat Intelligence Report

A narrative, executive‑ready view into the malware’s behavior, exposure, and reliable defenses.
Generated: 2025-12-04 08:22:12 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
doqdwrk.exe
Type
Win32 Executable MS Visual C++ (generic)
SHA‑1
3bac27f369950df4a9a4e36dba5953ebb1d02968
MD5
90e630e952a5539beb7304d6e29cc70a
First Seen
2025-12-02 11:33:16.474351
Last Analysis
2025-12-02 18:55:58.387523
Dwell Time
0 days, 7 hours, 33 minutes

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.

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-11-16 00:31:09 UTC First VirusTotal submission
2025-12-03 21:09:30 UTC Latest analysis snapshot 17 days, 20 hours, 38 minutes
2025-12-04 08:22:12 UTC Report generation time 18 days, 7 hours, 51 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

  • Acronis
  • CMC
  • Google
  • google_safebrowsing
  • SUPERAntiSpyware
  • TACHYON
  • tehtris

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 (42.06% 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 6714 42.06%
File System 4839 30.31%
Registry 2811 17.61%
Misc 890 5.58%
Process 196 1.23%
Device 176 1.10%
Com 135 0.85%
Threading 112 0.70%
Crypto 32 0.20%
Network 22 0.14%
Services 19 0.12%
Synchronization 8 0.05%
Hooking 6 0.04%
Windows 4 0.03%

MITRE ATT&CK Mapping

  • T1547.001 – reference startup folder
  • T1129 – link function at runtime on Windows
  • T1543.003 – create service
  • T1569.002 – create service
  • T1027.005 – contain obfuscated stackstrings
  • T1083 – get file size
  • T1543.003 – start service
  • T1543.003 – persist via Windows service
  • T1569.002 – persist via Windows service
  • T1543.003 – modify service
  • T1569.002 – modify service
  • T1497.001 – reference anti-VM strings
  • T1016 – get socket status
  • T1082 – get number of processors
  • T1497.001 – reference anti-VM strings targeting VirtualPC

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.msftncsi.com 23.200.3.20 United States Akamai Technologies, Inc.
www.aieov.com 13.248.169.48 United States Amazon Technologies Inc.
www.iuqerfsodp9ifjaposdfjhgosurijfaewrwergwea.com 104.16.167.228 United States Cloudflare, Inc.

Observed IPs

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

DNS Queries

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

Contacted IPs

IP Country ASN/Org
224.0.0.252
239.255.255.250
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 6 udp
53 54 udp
3702 1 udp

UDP Packets

Source IP Dest IP Sport Dport Time Proto
192.168.56.13 192.168.56.255 137 137 3.244205951690674 udp
192.168.56.13 224.0.0.252 49311 5355 5.732249021530151 udp
192.168.56.13 224.0.0.252 55150 5355 3.1729860305786133 udp
192.168.56.13 224.0.0.252 57310 5355 22.075114011764526 udp
192.168.56.13 224.0.0.252 60010 5355 5.183223009109497 udp
192.168.56.13 224.0.0.252 62406 5355 3.1806979179382324 udp
192.168.56.13 224.0.0.252 63527 5355 4.105475902557373 udp
192.168.56.13 239.255.255.250 52252 3702 3.1860108375549316 udp
192.168.56.13 8.8.4.4 50554 53 98.337406873703 udp
192.168.56.13 8.8.4.4 53518 53 203.11134099960327 udp
192.168.56.13 8.8.4.4 53985 53 330.822301864624 udp
192.168.56.13 8.8.4.4 54879 53 7.744318962097168 udp
192.168.56.13 8.8.4.4 54881 53 6.682739973068237 udp
192.168.56.13 8.8.4.4 55551 53 127.08766102790833 udp
192.168.56.13 8.8.4.4 55743 53 316.46273493766785 udp
192.168.56.13 8.8.4.4 56086 53 282.109974861145 udp
192.168.56.13 8.8.4.4 56197 53 112.69765090942383 udp
192.168.56.13 8.8.4.4 56908 53 345.2600049972534 udp
192.168.56.13 8.8.4.4 57065 53 220.1112699508667 udp
192.168.56.13 8.8.4.4 57415 53 36.431386947631836 udp
192.168.56.13 8.8.4.4 58070 53 359.6188290119171 udp
192.168.56.13 8.8.4.4 58697 53 8.401245832443237 udp
192.168.56.13 8.8.4.4 58920 53 51.181313037872314 udp
192.168.56.13 8.8.4.4 59610 53 252.71244287490845 udp
192.168.56.13 8.8.4.4 60543 53 174.80678296089172 udp
192.168.56.13 8.8.4.4 60780 53 267.0718820095062 udp
192.168.56.13 8.8.4.4 60910 53 65.5880298614502 udp
192.168.56.13 8.8.4.4 61004 53 145.68135690689087 udp
192.168.56.13 8.8.4.4 61800 53 302.1086678504944 udp
192.168.56.13 8.8.4.4 62422 53 373.9781379699707 udp
192.168.56.13 8.8.4.4 62493 53 23.056351900100708 udp
192.168.56.13 8.8.4.4 62849 53 22.042114973068237 udp
192.168.56.13 8.8.4.4 64533 53 160.0878529548645 udp
192.168.56.13 8.8.4.4 64801 53 79.99412083625793 udp
192.168.56.13 8.8.4.4 64886 53 234.4627709388733 udp
192.168.56.13 8.8.8.8 50554 53 97.33830094337463 udp
192.168.56.13 8.8.8.8 53518 53 202.11163187026978 udp
192.168.56.13 8.8.8.8 53985 53 329.82225584983826 udp
192.168.56.13 8.8.8.8 54879 53 8.74430799484253 udp
192.168.56.13 8.8.8.8 54881 53 7.681136846542358 udp
192.168.56.13 8.8.8.8 55551 53 126.09981489181519 udp
192.168.56.13 8.8.8.8 55743 53 315.4632730484009 udp
192.168.56.13 8.8.8.8 56086 53 281.1161289215088 udp
192.168.56.13 8.8.8.8 56197 53 111.70768690109253 udp
192.168.56.13 8.8.8.8 56908 53 344.26634788513184 udp
192.168.56.13 8.8.8.8 57065 53 219.11190104484558 udp
192.168.56.13 8.8.8.8 57415 53 35.432337045669556 udp
192.168.56.13 8.8.8.8 58070 53 358.6198868751526 udp
192.168.56.13 8.8.8.8 58697 53 9.400322914123535 udp
192.168.56.13 8.8.8.8 58920 53 50.18215584754944 udp
192.168.56.13 8.8.8.8 59610 53 251.713143825531 udp
192.168.56.13 8.8.8.8 60543 53 173.8158609867096 udp
192.168.56.13 8.8.8.8 60780 53 266.0727849006653 udp
192.168.56.13 8.8.8.8 60910 53 64.5881700515747 udp
192.168.56.13 8.8.8.8 61004 53 144.68659782409668 udp
192.168.56.13 8.8.8.8 61800 53 301.1183240413666 udp
192.168.56.13 8.8.8.8 62422 53 372.9791669845581 udp
192.168.56.13 8.8.8.8 62493 53 22.064360857009888 udp
192.168.56.13 8.8.8.8 62849 53 21.041141033172607 udp
192.168.56.13 8.8.8.8 64533 53 159.09058904647827 udp
192.168.56.13 8.8.8.8 64801 53 78.99512982368469 udp
192.168.56.13 8.8.8.8 64886 53 233.46305394172668 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