64-bit Keylogger Using Telegram/Smtp Indicators and Temp SFX Paths


Zero‑Dwell Threat Intelligence Report

A narrative, executive‑ready view into the malware’s behavior, exposure, and reliable defenses.
Generated: 2025-11-03 13:38:18 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
6264nyl.exe
Type
PE32+ executable (GUI) x86-64, for MS Windows
SHA‑1
4ef601add2dba6d0a4b16b217a1b8133005bd3ae
MD5
54b734bc6be8b4af3e00c203727e298a
First Seen
2025-09-14 13:36:43.144296
Last Analysis
2025-09-15 07:15:19.276785
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:46:31 UTC First VirusTotal submission
2025-09-19 06:42:41 UTC Latest analysis snapshot 6 days, 18 hours, 56 minutes
2025-11-03 13:38:18 UTC Report generation time 52 days, 1 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: 44. Missed: 29. Coverage: 60.3%.

Detected Vendors

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

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

Missed Vendors

  • Acronis
  • Antiy-AVL
  • APEX
  • Baidu
  • ClamAV
  • CMC
  • Cylance
  • DrWeb
  • Elastic
  • Fortinet
  • google_safebrowsing
  • Gridinsoft
  • huorong
  • Jiangmin
  • K7AntiVirus
  • K7GW
  • NANO-Antivirus
  • SentinelOne
  • SUPERAntiSpyware
  • TACHYON
  • tehtris
  • Trapmine
  • TrendMicro
  • ViRobot
  • Webroot
  • Yandex
  • 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 (50.91% 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 534 50.91%
System 234 22.31%
Process 228 21.73%
Windows 51 4.86%
Hooking 1 0.10%
Synchronization 1 0.10%

MITRE ATT&CK Mapping

  • T1027 – encode data using XOR
  • T1056.001 – log keystrokes via polling
  • T1115 – open clipboard
  • T1027.005 – contain obfuscated stackstrings
  • T1129 – link function at runtime on Windows
  • T1083 – get common file path
  • T1115 – read clipboard data
  • T1129 – link many functions at runtime
  • T1071 – Reads from the memory of another process
  • T1027 – encode data using XOR
  • T1056.001 – log keystrokes via polling
  • T1115 – open clipboard
  • T1115 – read clipboard data
  • T1129 – link function at runtime on Windows
  • T1083 – get common file path
  • T1129 – link many functions at runtime
  • T1056 – The process behaves as a keylogger (keyboard capturing detected)
  • T1027.005 – contain obfuscated stackstrings
  • 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 13.248.169.48 United States Amazon Technologies Inc.
www.msftncsi.com 23.200.3.20 United States Akamai 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
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 50 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.244297981262207 udp
192.168.56.11 224.0.0.252 49563 5355 3.173218011856079 udp
192.168.56.11 224.0.0.252 54650 5355 3.1753599643707275 udp
192.168.56.11 224.0.0.252 55601 5355 4.007544994354248 udp
192.168.56.11 224.0.0.252 60205 5355 3.1866068840026855 udp
192.168.56.11 224.0.0.252 62798 5355 5.7366979122161865 udp
192.168.56.11 239.255.255.250 62184 3702 3.180953025817871 udp
192.168.56.11 8.8.4.4 50586 53 343.0414168834686 udp
192.168.56.11 8.8.4.4 51628 53 112.19711685180664 udp
192.168.56.11 8.8.4.4 51663 53 173.52553391456604 udp
192.168.56.11 8.8.4.4 51690 53 6.572906017303467 udp
192.168.56.11 8.8.4.4 51880 53 206.13510584831238 udp
192.168.56.11 8.8.4.4 51899 53 5.74451208114624 udp
192.168.56.11 8.8.4.4 52464 53 314.4315369129181 udp
192.168.56.11 8.8.4.4 53480 53 238.7444188594818 udp
192.168.56.11 8.8.4.4 54684 53 285.7131290435791 udp
192.168.56.11 8.8.4.4 55183 53 357.4007019996643 udp
192.168.56.11 8.8.4.4 56213 53 36.29079294204712 udp
192.168.56.11 8.8.4.4 56473 53 97.83825898170471 udp
192.168.56.11 8.8.4.4 56666 53 220.49443197250366 udp
192.168.56.11 8.8.4.4 58090 53 267.4630949497223 udp
192.168.56.11 8.8.4.4 58800 53 328.68186497688293 udp
192.168.56.11 8.8.4.4 58917 53 79.58779907226562 udp
192.168.56.11 8.8.4.4 59770 53 50.86891293525696 udp
192.168.56.11 8.8.4.4 60054 53 253.10370588302612 udp
192.168.56.11 8.8.4.4 60334 53 126.5563600063324 udp
192.168.56.11 8.8.4.4 61507 53 144.80693006515503 udp
192.168.56.11 8.8.4.4 62120 53 159.16609406471252 udp
192.168.56.11 8.8.4.4 62329 53 65.22818303108215 udp
192.168.56.11 8.8.4.4 63439 53 21.93173384666443 udp
192.168.56.11 8.8.4.4 63550 53 191.77533197402954 udp
192.168.56.11 8.8.4.4 64563 53 300.07191491127014 udp
192.168.56.11 8.8.8.8 50586 53 342.0419919490814 udp
192.168.56.11 8.8.8.8 51628 53 111.1978440284729 udp
192.168.56.11 8.8.8.8 51663 53 172.52574706077576 udp
192.168.56.11 8.8.8.8 51690 53 7.572540044784546 udp
192.168.56.11 8.8.8.8 51880 53 205.1354649066925 udp
192.168.56.11 8.8.8.8 51899 53 6.744050025939941 udp
192.168.56.11 8.8.8.8 52464 53 313.43270802497864 udp
192.168.56.11 8.8.8.8 53480 53 237.74464297294617 udp
192.168.56.11 8.8.8.8 54684 53 284.71362805366516 udp
192.168.56.11 8.8.8.8 55183 53 356.4012839794159 udp
192.168.56.11 8.8.8.8 56213 53 35.29159998893738 udp
192.168.56.11 8.8.8.8 56473 53 96.83854794502258 udp
192.168.56.11 8.8.8.8 56666 53 219.4945089817047 udp
192.168.56.11 8.8.8.8 58090 53 266.46340894699097 udp
192.168.56.11 8.8.8.8 58800 53 327.68273091316223 udp
192.168.56.11 8.8.8.8 58917 53 78.58874487876892 udp
192.168.56.11 8.8.8.8 59770 53 49.86997389793396 udp
192.168.56.11 8.8.8.8 60054 53 252.10391092300415 udp
192.168.56.11 8.8.8.8 60334 53 125.5573239326477 udp
192.168.56.11 8.8.8.8 61507 53 143.8086769580841 udp
192.168.56.11 8.8.8.8 62120 53 158.16676592826843 udp
192.168.56.11 8.8.8.8 62329 53 64.22943592071533 udp
192.168.56.11 8.8.8.8 63439 53 20.9327130317688 udp
192.168.56.11 8.8.8.8 63550 53 190.77795600891113 udp
192.168.56.11 8.8.8.8 64563 53 299.07637095451355 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