Analysis

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

    arch:x64arch:x86image:win10v2004-20241007-enlocale:en-usos:windows10-2004-x64system
  • submitted
    19/11/2024, 18:51

General

  • Target

    7bb679fd3535464237922aac06d99bcd687e4a1c4ccc825e0986981e0eed7c49.xls

  • Size

    95KB

  • MD5

    2d3b1a5dad99e32f133e13f260519b6a

  • SHA1

    3f488f1f85d6daa8d4376a8c232b9efc209a1c41

  • SHA256

    7bb679fd3535464237922aac06d99bcd687e4a1c4ccc825e0986981e0eed7c49

  • SHA512

    40b022c41cf0c2b57182134fb02a2e5d25858b0cc89d4b5919f05f229758e174796f81b934ebb79dd7564830f6b173d0805633902e29fd007e10a5d557e7583e

  • SSDEEP

    1536:PFKpb8rGYrMPe3q7Q0XV5xtezEsi8/dgCHuS4hcTO97v7UYdEJmor:tKpb8rGYrMPe3q7Q0XV5xtezEsi8/dg+

Score
10/10

Malware Config

Extracted

Language
xlm4.0
Source
URLs
xlm40.dropper

http://www.sunflowerlaboratory.in/fonts/79Tq62ly/

xlm40.dropper

http://dirigent.co.uk/vardagsekonomi/iC36jJ4J1cf/

xlm40.dropper

http://agtrade.hu/images/kiQYmOs2tSKq/

xlm40.dropper

https://www.zachboyle.com/wp-admin/EA470ZrTGNkuA/

Signatures

  • Process spawned unexpected child process 4 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 8 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\7bb679fd3535464237922aac06d99bcd687e4a1c4ccc825e0986981e0eed7c49.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:2580
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\soci1.ocx
      2⤵
      • Process spawned unexpected child process
      PID:2480
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\soci2.ocx
      2⤵
      • Process spawned unexpected child process
      PID:2352
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\soci3.ocx
      2⤵
      • Process spawned unexpected child process
      PID:3052
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\soci4.ocx
      2⤵
      • Process spawned unexpected child process
      PID:2344

Network

MITRE ATT&CK Enterprise v15

Replay Monitor

Loading Replay Monitor...

Downloads

  • memory/2580-1-0x00007FFD6E98D000-0x00007FFD6E98E000-memory.dmp

    Filesize

    4KB

  • memory/2580-0-0x00007FFD2E970000-0x00007FFD2E980000-memory.dmp

    Filesize

    64KB

  • memory/2580-3-0x00007FFD2E970000-0x00007FFD2E980000-memory.dmp

    Filesize

    64KB

  • memory/2580-4-0x00007FFD2E970000-0x00007FFD2E980000-memory.dmp

    Filesize

    64KB

  • memory/2580-5-0x00007FFD2E970000-0x00007FFD2E980000-memory.dmp

    Filesize

    64KB

  • memory/2580-2-0x00007FFD2E970000-0x00007FFD2E980000-memory.dmp

    Filesize

    64KB

  • memory/2580-6-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-8-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-7-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-10-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-9-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-11-0x00007FFD2C550000-0x00007FFD2C560000-memory.dmp

    Filesize

    64KB

  • memory/2580-13-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-14-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-15-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-16-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-18-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-19-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-20-0x00007FFD2C550000-0x00007FFD2C560000-memory.dmp

    Filesize

    64KB

  • memory/2580-17-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-12-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-44-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-45-0x00007FFD6E98D000-0x00007FFD6E98E000-memory.dmp

    Filesize

    4KB

  • memory/2580-46-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB

  • memory/2580-50-0x00007FFD6E8F0000-0x00007FFD6EAE5000-memory.dmp

    Filesize

    2.0MB