ClipBanker Stealer Masquerades as UserOOBEBroker.exe


Zero‑Dwell Threat Intelligence Report

A narrative, executive‑ready view into the malware’s behavior, exposure, and reliable defenses.
Generated: 2025-10-27 10:19:20 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
atobvt.exe
Type
PE32 executable (GUI) Intel 80386 Mono/.Net assembly, for MS Windows
SHA‑1
83754ed1d478285dfb9c68341edb2461a0b3ba13
MD5
1a89e7227279765b3a92f5558b56d563
First Seen
2025-09-14 13:50:19.441517
Last Analysis
2025-09-15 07:15:21.279090
Dwell Time
0 days, 7 hours, 33 minutes

Extended Dwell Time Impact

For 17+ hours, this malware remained undetected — a half-day window that permitted the adversary to complete initial execution, establish basic persistence, and perform initial system enumeration.

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-12 15:17:03 UTC First VirusTotal submission
2025-09-19 06:44:48 UTC Latest analysis snapshot 6 days, 15 hours, 27 minutes
2025-10-27 10:19:20 UTC Report generation time 44 days, 19 hours, 2 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: 51. Missed: 22. Coverage: 69.9%.

Detected Vendors

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

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

Missed Vendors

  • Acronis
  • Antiy-AVL
  • Baidu
  • ClamAV
  • CMC
  • Cynet
  • DrWeb
  • google_safebrowsing
  • Jiangmin
  • Kaspersky
  • MaxSecure
  • NANO-Antivirus
  • Rising
  • SUPERAntiSpyware
  • TACHYON
  • tehtris
  • TrendMicro
  • ViRobot
  • Webroot
  • Yandex
  • Zillya
  • 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 (37.84% 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 521 37.84%
Registry 362 26.29%
File System 219 15.90%
Process 144 10.46%
Misc 75 5.45%
Crypto 24 1.74%
Synchronization 14 1.02%
Threading 10 0.73%
Device 4 0.29%
Hooking 2 0.15%
Windows 2 0.15%

MITRE ATT&CK Mapping

  • No MITRE ATT&CK techniques detected

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 76.223.54.146 United States Amazon.com, 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
www.msftncsi.com A
5isohu.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 6 udp
3702 1 udp

UDP Packets

Source IP Dest IP Sport Dport Time Proto
192.168.56.11 192.168.56.255 137 137 3.2446529865264893 udp
192.168.56.11 224.0.0.252 49563 5355 3.1824209690093994 udp
192.168.56.11 224.0.0.252 54650 5355 3.187001943588257 udp
192.168.56.11 224.0.0.252 55601 5355 3.910188913345337 udp
192.168.56.11 224.0.0.252 60205 5355 3.20113205909729 udp
192.168.56.11 224.0.0.252 62798 5355 5.7502100467681885 udp
192.168.56.11 239.255.255.250 62184 3702 3.1973650455474854 udp
192.168.56.11 8.8.4.4 51690 53 6.479814052581787 udp
192.168.56.11 8.8.4.4 51899 53 5.786848068237305 udp
192.168.56.11 8.8.4.4 63439 53 21.93216896057129 udp
192.168.56.11 8.8.8.8 51690 53 7.463608980178833 udp
192.168.56.11 8.8.8.8 51899 53 6.7756829261779785 udp
192.168.56.11 8.8.8.8 63439 53 20.933568000793457 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