Analysis

  • max time kernel
    133s
  • max time network
    138s
  • 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, 10:26

General

  • Target

    3de6e152fbe4de6db133082ce82a68cba9d5c7cc48a51caba755a9441d0fc2c0.xlsm

  • Size

    35KB

  • MD5

    fb5bfafec7ad3aceae2ab864c5f42fe1

  • SHA1

    c570d2f2d933a27fe02a0c2b5416a0dae1011c84

  • SHA256

    3de6e152fbe4de6db133082ce82a68cba9d5c7cc48a51caba755a9441d0fc2c0

  • SHA512

    01cb93465b941ea8b98f53eafa6b70ef41d41ddde6ab867e42979e21c5d0222f8e763a306bb19232d2256a31f066898fb4a627db28e9a208ee49a9ee9abe945d

  • SSDEEP

    768:qYKtm5eMn7AjOZpqcVbZYpoRuBlIiOKMArOooooooooooooooooooooooooooXLR:qYKtmg+UOZZ1ZYpoQ/pMAm

Score
10/10

Malware Config

Extracted

Language
xlm4.0
Source
URLs
xlm40.dropper

https://casinojackpotking.com/cgi-bin/47sKbklSQf31/

Signatures

  • Process spawned unexpected child process 1 IoCs

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

  • System Location Discovery: System Language Discovery 1 TTPs 1 IoCs

    Attempt gather information about the system language of a victim in order to infer the geographical location of that host.

  • 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 3 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\3de6e152fbe4de6db133082ce82a68cba9d5c7cc48a51caba755a9441d0fc2c0.xlsm"
    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:3036
    • C:\Windows\SysWow64\regsvr32.exe
      C:\Windows\SysWow64\regsvr32.exe -s ..\xdha.ocx
      2⤵
      • Process spawned unexpected child process
      • System Location Discovery: System Language Discovery
      PID:1468

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

    3KB

    MD5

    0c869030243d7624c8a3f7d8af1633f6

    SHA1

    875e789e545ccb62468ddbf03bea6586213764a4

    SHA256

    a20c3eb06097d65955a14d5f8d65ea85fc9e0e495356b1c9bc6c2d002f5047ae

    SHA512

    7274962121980ed50492335d8f5fc32ec5d3e293a3f1e8952f1bcc5d0865a77801a2110130fc0b6a2a45b929bed05f681439efc6f103e07dc38cbda31373d1ab

  • C:\Users\Admin\xdha.ocx

    Filesize

    9B

    MD5

    9d1ead73e678fa2f51a70a933b0bf017

    SHA1

    d205cbd6783332a212c5ae92d73c77178c2d2f28

    SHA256

    0019dfc4b32d63c1392aa264aed2253c1e0c2fb09216f8e2cc269bbfb8bb49b5

    SHA512

    935b3d516e996f6d25948ba8a54c1b7f70f7f0e3f517e36481fdf0196c2c5cfc2841f86e891f3df9517746b7fb605db47cdded1b8ff78d9482ddaa621db43a34

  • memory/3036-14-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-10-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-2-0x00007FF7F2D90000-0x00007FF7F2DA0000-memory.dmp

    Filesize

    64KB

  • memory/3036-0-0x00007FF7F2D90000-0x00007FF7F2DA0000-memory.dmp

    Filesize

    64KB

  • memory/3036-6-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-8-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-7-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-16-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-13-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-12-0x00007FF7F0530000-0x00007FF7F0540000-memory.dmp

    Filesize

    64KB

  • memory/3036-5-0x00007FF7F2D90000-0x00007FF7F2DA0000-memory.dmp

    Filesize

    64KB

  • memory/3036-3-0x00007FF832DAD000-0x00007FF832DAE000-memory.dmp

    Filesize

    4KB

  • memory/3036-11-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-18-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-17-0x00007FF7F0530000-0x00007FF7F0540000-memory.dmp

    Filesize

    64KB

  • memory/3036-20-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-21-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-19-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-15-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-9-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-4-0x00007FF7F2D90000-0x00007FF7F2DA0000-memory.dmp

    Filesize

    64KB

  • memory/3036-39-0x00007FF832D10000-0x00007FF832F05000-memory.dmp

    Filesize

    2.0MB

  • memory/3036-1-0x00007FF7F2D90000-0x00007FF7F2DA0000-memory.dmp

    Filesize

    64KB