Malicious DLL Uses Advapi32/Bcrypt Calls for Stealthy Persistence


Zero‑Dwell Threat Intelligence Report

A narrative, executive‑ready view into the malware’s behavior, exposure, and reliable defenses.
Generated: 2025-11-05 07:03: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
qgyxnbx.exe
Type
PE32+ executable (DLL) (GUI) x86-64, for MS Windows
SHA‑1
52653f7c98671506eb10934875b41821ce50c837
MD5
19c2f688052a60db10ecb88eee9b49df
First Seen
2025-09-14 13:40:38.281760
Last Analysis
2025-09-15 07:15:19.796907
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 11:16:06 UTC First VirusTotal submission
2025-09-19 06:42:52 UTC Latest analysis snapshot 6 days, 19 hours, 26 minutes
2025-11-05 07:03:12 UTC Report generation time 53 days, 19 hours, 47 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: 52. Missed: 21. Coverage: 71.2%.

Detected Vendors

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

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

Missed Vendors

  • Acronis
  • Alibaba
  • Antiy-AVL
  • APEX
  • Baidu
  • ClamAV
  • CMC
  • CrowdStrike
  • DrWeb
  • huorong
  • NANO-Antivirus
  • Sangfor
  • SentinelOne
  • SUPERAntiSpyware
  • TACHYON
  • tehtris
  • Trapmine
  • VirIT
  • Zillya
  • ZoneAlarm
  • 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 (45.61% 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 109 45.61%
System 69 28.87%
Process 53 22.18%
Registry 8 3.35%

MITRE ATT&CK Mapping

  • T1129 – link many functions at runtime
  • T1129 – access PEB ldr_data
  • T1082 – get number of processors
  • T1027 – hash data via BCrypt
  • T1129 – link function at runtime on Windows
  • T1027 – encode data using XOR
  • T1082 – get system information on Windows
  • T1082 – query environment variable
  • T1027 – reference Base64 string
  • T1134 – modify access privileges
  • T1082 – get memory capacity
  • T1012 – query or enumerate registry value
  • T1614 – get geographical location
  • T1129 – The process tried to load dynamically one or more functions.
  • T1045 – Manalize Local SandBox Packer Harvesting
  • T1129 – access PEB ldr_data
  • T1027 – encode data using XOR
  • T1129 – link function at runtime on Windows
  • T1082 – query environment variable
  • T1082 – get memory capacity
  • T1082 – get system information on Windows
  • T1134 – modify access privileges
  • T1129 – link many functions at runtime
  • T1055 – write process memory
  • T1614 – get geographical location
  • T1012 – query or enumerate registry value
  • T1027 – hash data via BCrypt
  • T1027 – reference Base64 string
  • T1063 – It Tries to detect injection methods

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 3 udp
53 48 udp

UDP Packets

Source IP Dest IP Sport Dport Time Proto
192.168.56.14 192.168.56.255 137 137 3.0071592330932617 udp
192.168.56.14 224.0.0.252 51209 5355 3.5017101764678955 udp
192.168.56.14 224.0.0.252 53401 5355 5.251050233840942 udp
192.168.56.14 224.0.0.252 55848 5355 5.168469190597534 udp
192.168.56.14 8.8.4.4 49916 53 113.34363007545471 udp
192.168.56.14 8.8.4.4 50180 53 160.3127510547638 udp
192.168.56.14 8.8.4.4 50710 53 80.73419308662415 udp
192.168.56.14 8.8.4.4 50870 53 329.82838010787964 udp
192.168.56.14 8.8.4.4 50914 53 254.25024700164795 udp
192.168.56.14 8.8.4.4 51262 53 315.57810401916504 udp
192.168.56.14 8.8.4.4 52815 53 23.07788920402527 udp
192.168.56.14 8.8.4.4 53449 53 358.54688906669617 udp
192.168.56.14 8.8.4.4 54579 53 66.37482023239136 udp
192.168.56.14 8.8.4.4 54683 53 207.28153705596924 udp
192.168.56.14 8.8.4.4 55094 53 7.733960151672363 udp
192.168.56.14 8.8.4.4 55827 53 268.60976910591125 udp
192.168.56.14 8.8.4.4 55914 53 145.9533290863037 udp
192.168.56.14 8.8.4.4 56399 53 192.92205023765564 udp
192.168.56.14 8.8.4.4 59068 53 344.18775606155396 udp
192.168.56.14 8.8.4.4 60117 53 98.98463916778564 udp
192.168.56.14 8.8.4.4 60713 53 286.85931611061096 udp
192.168.56.14 8.8.4.4 62022 53 174.67243003845215 udp
192.168.56.14 8.8.4.4 62112 53 52.01536321640015 udp
192.168.56.14 8.8.4.4 62548 53 239.89059710502625 udp
192.168.56.14 8.8.4.4 62800 53 301.2186071872711 udp
192.168.56.14 8.8.4.4 63205 53 221.6411271095276 udp
192.168.56.14 8.8.4.4 64753 53 127.7033920288086 udp
192.168.56.14 8.8.4.4 65148 53 37.43717622756958 udp
192.168.56.14 8.8.8.8 49916 53 112.34411311149597 udp
192.168.56.14 8.8.8.8 50180 53 159.31330013275146 udp
192.168.56.14 8.8.8.8 50710 53 79.73492622375488 udp
192.168.56.14 8.8.8.8 50870 53 328.82949709892273 udp
192.168.56.14 8.8.8.8 50914 53 253.2508761882782 udp
192.168.56.14 8.8.8.8 51262 53 314.5786190032959 udp
192.168.56.14 8.8.8.8 52815 53 22.078702211380005 udp
192.168.56.14 8.8.8.8 53449 53 357.5473082065582 udp
192.168.56.14 8.8.8.8 54579 53 65.37505006790161 udp
192.168.56.14 8.8.8.8 54683 53 206.281729221344 udp
192.168.56.14 8.8.8.8 55094 53 8.718516111373901 udp
192.168.56.14 8.8.8.8 55827 53 267.6100981235504 udp
192.168.56.14 8.8.8.8 55914 53 144.9539361000061 udp
192.168.56.14 8.8.8.8 56399 53 191.92369318008423 udp
192.168.56.14 8.8.8.8 59068 53 343.18803906440735 udp
192.168.56.14 8.8.8.8 60117 53 97.99778509140015 udp
192.168.56.14 8.8.8.8 60713 53 285.859530210495 udp
192.168.56.14 8.8.8.8 62022 53 173.67226815223694 udp
192.168.56.14 8.8.8.8 62112 53 51.01606011390686 udp
192.168.56.14 8.8.8.8 62548 53 238.89101600646973 udp
192.168.56.14 8.8.8.8 62800 53 300.2194631099701 udp
192.168.56.14 8.8.8.8 63205 53 220.64095520973206 udp
192.168.56.14 8.8.8.8 64753 53 126.70379900932312 udp
192.168.56.14 8.8.8.8 65148 53 36.43775415420532 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