Berbew Trojan Loader Using WININET and Winsock for C2 Communications


Zero‑Dwell Threat Intelligence Report

A narrative, executive‑ready view into the malware’s behavior, exposure, and reliable defenses.
Generated: 2025-11-11 23:28:51 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
0w5ds8dd.exe
Type
PE32 executable (GUI) Intel 80386, for MS Windows
SHA‑1
dc2894a2ddb415486af840662796b1a5197a03fd
MD5
c17da8f1107bbddcb385c8c2721e22fb
First Seen
2025-10-06 07:13:30.059886
Last Analysis
2025-10-06 13:37:17.878825
Dwell Time
0 days, 7 hours, 33 minutes

Extended Dwell Time Impact

For 6+ 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-09-01 18:51:33 UTC First VirusTotal submission
2025-10-08 14:09:15 UTC Latest analysis snapshot 36 days, 19 hours, 17 minutes
2025-11-11 23:28:51 UTC Report generation time 64 days, 12 hours, 22 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: 67. Missed: 6. Coverage: 91.8%.

Detected Vendors

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

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

Missed Vendors

  • CMC
  • google_safebrowsing
  • SUPERAntiSpyware
  • TrendMicro
  • 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

Intensive file system activity (59.66% of behavior) indicates data harvesting, file encryption, or dropper behavior. The threat is actively searching for and manipulating files across the system.

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
File System 92187 59.66%
System 51156 33.11%
Process 6453 4.18%
Registry 3439 2.23%
Misc 647 0.42%
Synchronization 214 0.14%
Hooking 213 0.14%
Threading 180 0.12%
Network 15 0.01%
Device 12 0.01%
Services 8 0.01%
__Notification__ 1 0.00%

MITRE ATT&CK Mapping

  • T1027.002 – packed with generic packer
  • T1027 – encode data using XOR

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 2.18.67.81 Europe Akamai Technologies
www.aieov.com 13.248.169.48 United States Amazon Technologies 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.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 5 udp
53 46 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.244550943374634 udp
192.168.56.13 224.0.0.252 49311 5355 5.736867904663086 udp
192.168.56.13 224.0.0.252 55150 5355 3.1730799674987793 udp
192.168.56.13 224.0.0.252 60010 5355 5.2463459968566895 udp
192.168.56.13 224.0.0.252 62406 5355 3.1754088401794434 udp
192.168.56.13 224.0.0.252 63527 5355 4.320570945739746 udp
192.168.56.13 239.255.255.250 52252 3702 3.1822030544281006 udp
192.168.56.13 8.8.4.4 50554 53 138.21260786056519 udp
192.168.56.13 8.8.4.4 53518 53 253.1231608390808 udp
192.168.56.13 8.8.4.4 54879 53 7.813237905502319 udp
192.168.56.13 8.8.4.4 54881 53 6.927387952804565 udp
192.168.56.13 8.8.4.4 55551 53 175.94690084457397 udp
192.168.56.13 8.8.4.4 56086 53 333.90065598487854 udp
192.168.56.13 8.8.4.4 56197 53 161.5875289440155 udp
192.168.56.13 8.8.4.4 57065 53 267.5100100040436 udp
192.168.56.13 8.8.4.4 57310 53 43.993901014328 udp
192.168.56.13 8.8.4.4 57415 53 59.415688037872314 udp
192.168.56.13 8.8.4.4 58697 53 25.665940046310425 udp
192.168.56.13 8.8.4.4 58920 53 82.7591278553009 udp
192.168.56.13 8.8.4.4 59610 53 305.10665798187256 udp
192.168.56.13 8.8.4.4 60543 53 228.74413585662842 udp
192.168.56.13 8.8.4.4 60780 53 319.5407249927521 udp
192.168.56.13 8.8.4.4 60910 53 101.99369883537292 udp
192.168.56.13 8.8.4.4 61004 53 196.14980483055115 udp
192.168.56.13 8.8.4.4 61800 53 340.1191689968109 udp
192.168.56.13 8.8.4.4 62493 53 40.02550387382507 udp
192.168.56.13 8.8.4.4 62849 53 29.30672788619995 udp
192.168.56.13 8.8.4.4 64533 53 211.66614603996277 udp
192.168.56.13 8.8.4.4 64801 53 117.8067090511322 udp
192.168.56.13 8.8.4.4 64886 53 281.86890983581543 udp
192.168.56.13 8.8.8.8 50554 53 137.21581888198853 udp
192.168.56.13 8.8.8.8 53518 53 252.10471487045288 udp
192.168.56.13 8.8.8.8 54879 53 8.815114974975586 udp
192.168.56.13 8.8.8.8 54881 53 7.91598105430603 udp
192.168.56.13 8.8.8.8 55551 53 174.94827389717102 udp
192.168.56.13 8.8.8.8 56086 53 332.9003999233246 udp
192.168.56.13 8.8.8.8 56197 53 160.59754705429077 udp
192.168.56.13 8.8.8.8 57065 53 266.51011204719543 udp
192.168.56.13 8.8.8.8 57310 53 43.00465202331543 udp
192.168.56.13 8.8.8.8 57415 53 58.42449188232422 udp
192.168.56.13 8.8.8.8 58697 53 24.66692304611206 udp
192.168.56.13 8.8.8.8 58920 53 81.76066398620605 udp
192.168.56.13 8.8.8.8 59610 53 304.1061918735504 udp
192.168.56.13 8.8.8.8 60543 53 227.74980998039246 udp
192.168.56.13 8.8.8.8 60780 53 318.54095482826233 udp
192.168.56.13 8.8.8.8 60910 53 101.00294399261475 udp
192.168.56.13 8.8.8.8 61004 53 195.15087485313416 udp
192.168.56.13 8.8.8.8 61800 53 339.13080286979675 udp
192.168.56.13 8.8.8.8 62493 53 39.027796030044556 udp
192.168.56.13 8.8.8.8 62849 53 28.311557054519653 udp
192.168.56.13 8.8.8.8 64533 53 210.67130494117737 udp
192.168.56.13 8.8.8.8 64801 53 116.81611895561218 udp
192.168.56.13 8.8.8.8 64886 53 280.86966586112976 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