Analysis

  • max time kernel
    149s
  • max time network
    152s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20241007-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20241007-enlocale:en-usos:windows10-2004-x64system
  • submitted
    20/11/2024, 13:06

General

  • Target

    0316acad3c847cb3c98a8f85b3304002130f409a0e9ce4b3741e02d68e9a5028.xls

  • Size

    70KB

  • MD5

    cef843f32f039091b7603114d38ddc9f

  • SHA1

    6dd9eeee832003fd1c2aec6f1ac42ca92fc3b801

  • SHA256

    0316acad3c847cb3c98a8f85b3304002130f409a0e9ce4b3741e02d68e9a5028

  • SHA512

    af5895e65b36a559fa46b75d504a1837d23e916e9f0293ba1d3be4f1b8c7dbd198dfa446f04286c538abe9a9003af918b6fc91b5d70de421565bec368d8438df

  • SSDEEP

    1536:OhKpb8rGYrMPe3q7Q0XV5xtezE8vG8UM+e+hDcnTLiQrRTZws8Egk:uKpb8rGYrMPe3q7Q0XV5xtezE8vG8UMx

Score
10/10

Malware Config

Extracted

Language
xlm4.0
Source
URLs
xlm40.dropper

https://strachanclark.com/images/3gc4qCpSFYbBMDEC/

xlm40.dropper

https://synapse-archive.com/images/bKaMr/

xlm40.dropper

https://sumuvesa.com/wp-includes/rgL/

Signatures

  • Process spawned unexpected child process 3 IoCs

    This typically indicates the parent process was compromised via an exploit or macro.

  • 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 FindShellTrayWindow 2 IoCs
  • Suspicious use of SetWindowsHookEx 12 IoCs
  • Suspicious use of WriteProcessMemory 6 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\0316acad3c847cb3c98a8f85b3304002130f409a0e9ce4b3741e02d68e9a5028.xls"
    1⤵
    • Checks processor information in registry
    • Enumerates system info in registry
    • Suspicious behavior: AddClipboardFormatListener
    • Suspicious use of FindShellTrayWindow
    • Suspicious use of SetWindowsHookEx
    • Suspicious use of WriteProcessMemory
    PID:3396
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\cusoa1.ocx
      2⤵
      • Process spawned unexpected child process
      PID:4040
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\cusoa2.ocx
      2⤵
      • Process spawned unexpected child process
      PID:2480
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\cusoa3.ocx
      2⤵
      • Process spawned unexpected child process
      PID:2880

Network

MITRE ATT&CK Enterprise v15

Replay Monitor

Loading Replay Monitor...

Downloads

  • C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\b8ab77100df80ab2.customDestinations-ms

    Filesize

    2KB

    MD5

    fe5a84cb365239eb0c5941c4384b7355

    SHA1

    b22b4395f8f6e34b46e9d8475a40a4d22771f637

    SHA256

    8f55cc33a253b0181dbddca43efba7aa65bc18632ec5cc0e05a5e8bdc92da7df

    SHA512

    180a47907a9e06aef67121408fb5aeb974d6a4add0053e6e7e28c45fcf6ee3f2ba3aca13aaeb04e02b4b525c2496208748667e7e99453a1a9354e4f53f4759cb

  • memory/3396-7-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-50-0x00007FFE768CD000-0x00007FFE768CE000-memory.dmp

    Filesize

    4KB

  • memory/3396-2-0x00007FFE368B0000-0x00007FFE368C0000-memory.dmp

    Filesize

    64KB

  • memory/3396-1-0x00007FFE768CD000-0x00007FFE768CE000-memory.dmp

    Filesize

    4KB

  • memory/3396-5-0x00007FFE368B0000-0x00007FFE368C0000-memory.dmp

    Filesize

    64KB

  • memory/3396-9-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-8-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-11-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-12-0x00007FFE34000000-0x00007FFE34010000-memory.dmp

    Filesize

    64KB

  • memory/3396-10-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-13-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-0-0x00007FFE368B0000-0x00007FFE368C0000-memory.dmp

    Filesize

    64KB

  • memory/3396-4-0x00007FFE368B0000-0x00007FFE368C0000-memory.dmp

    Filesize

    64KB

  • memory/3396-6-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-19-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-17-0x00007FFE34000000-0x00007FFE34010000-memory.dmp

    Filesize

    64KB

  • memory/3396-18-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-21-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-15-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-20-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-16-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-49-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-14-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-51-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-55-0x00007FFE76830000-0x00007FFE76A25000-memory.dmp

    Filesize

    2.0MB

  • memory/3396-3-0x00007FFE368B0000-0x00007FFE368C0000-memory.dmp

    Filesize

    64KB