Analysis

  • max time kernel
    133s
  • max time network
    129s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20250217-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20250217-enlocale:en-usos:windows10-2004-x64system
  • submitted
    05/03/2025, 13:05

General

  • Target

    $TEMP/Xnxx.xltm

  • Size

    56KB

  • MD5

    6b838b964a714ceb075c1530d92c46fb

  • SHA1

    17cfee6ed0cc62ffbfbb3045c6985da8cf072863

  • SHA256

    e053dc79bb7255ec9f393ee70eb38c311a08b3ff77bc3646a00bcebdd95a7dd5

  • SHA512

    f767fa79da73ed50d530d246efb14d7f766f3678f29e7091965b58f5c2a950de3c5373e03d4d58b51ab35880db1113c346735ba086cfc477d1ad061e270cbf3e

  • SSDEEP

    1536:NkdZfrEiCK5HYKGnINbA7+J7jMh8HsXQMuG:NRiZ4GNVwhKk

Score
1/10

Malware Config

Signatures

  • Checks processor information in registry 2 TTPs 3 IoCs

    Processor information is often read in order to detect sandboxing environments.

  • Enumerates system info in registry 2 TTPs 3 IoCs
  • Suspicious behavior: AddClipboardFormatListener 1 IoCs
  • Suspicious use of SetWindowsHookEx 9 IoCs

Processes

  • C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXE
    "C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXE" "C:\Users\Admin\AppData\Local\Temp\$TEMP\Xnxx.xltm"
    1⤵
    • Checks processor information in registry
    • Enumerates system info in registry
    • Suspicious behavior: AddClipboardFormatListener
    • Suspicious use of SetWindowsHookEx
    PID:5016

Network

MITRE ATT&CK Enterprise v15

Replay Monitor

Loading Replay Monitor...

Downloads

  • memory/5016-0-0x00007FF818CB0000-0x00007FF818CC0000-memory.dmp

    Filesize

    64KB

  • memory/5016-1-0x00007FF858CCD000-0x00007FF858CCE000-memory.dmp

    Filesize

    4KB

  • memory/5016-2-0x00007FF818CB0000-0x00007FF818CC0000-memory.dmp

    Filesize

    64KB

  • memory/5016-3-0x00007FF818CB0000-0x00007FF818CC0000-memory.dmp

    Filesize

    64KB

  • memory/5016-4-0x00007FF818CB0000-0x00007FF818CC0000-memory.dmp

    Filesize

    64KB

  • memory/5016-9-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-8-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-10-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-11-0x00007FF816720000-0x00007FF816730000-memory.dmp

    Filesize

    64KB

  • memory/5016-7-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-6-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-15-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-20-0x00007FF816720000-0x00007FF816730000-memory.dmp

    Filesize

    64KB

  • memory/5016-19-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-21-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-18-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-17-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-16-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-14-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-13-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-12-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-5-0x00007FF818CB0000-0x00007FF818CC0000-memory.dmp

    Filesize

    64KB

  • memory/5016-32-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-33-0x00007FF858CCD000-0x00007FF858CCE000-memory.dmp

    Filesize

    4KB

  • memory/5016-34-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB

  • memory/5016-35-0x00007FF858C30000-0x00007FF858E25000-memory.dmp

    Filesize

    2.0MB