Analysis

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

    arch:x64arch:x86image:win10v2004-20240802-enlocale:en-usos:windows10-2004-x64system
  • submitted
    05-09-2024 19:20

General

  • Target

    PaymentStatus.xls

  • Size

    216KB

  • MD5

    2486374800299563ab8934122234242a

  • SHA1

    47bfe94aa96ef43231890f04ccd286b0888e10c8

  • SHA256

    ef2ce641a4e9f270eea626e8e4800b0b97b4a436c40e7af30aeb6f02566b809c

  • SHA512

    74e52e1e1317908447340cbba32949321ed435f17a524224af80236ecdf67187c83908cca514e82a49b9abe9495125ba741e01ed8f30663124c13fce339c63e5

  • SSDEEP

    6144:bKpb8rGYrMPe3q7Q0XV5xtuEsi8/dgAyY+TAQXTHGUMEyP5p6f5jQmK:GbGUMVWlbK

Score
10/10

Malware Config

Extracted

Language
xlm4.0
Source
URLs
xlm40.dropper

https://audioselec.com/about/dDw5ggtyMojggTqhc/

xlm40.dropper

https://geringer-muehle.de/wp-admin/G/

xlm40.dropper

http://intolove.co.uk/wp-admin/FbGhiWtrEzrQ/

xlm40.dropper

http://isc.net.ua/themes/3rU/

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 14 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\PaymentStatus.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:5104
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe ..\oxnv1.ooccxx
      2⤵
      • Process spawned unexpected child process
      PID:2396
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe ..\oxnv2.ooccxx
      2⤵
      • Process spawned unexpected child process
      PID:2644
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe ..\oxnv3.ooccxx
      2⤵
      • Process spawned unexpected child process
      PID:1180
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe ..\oxnv4.ooccxx
      2⤵
      • Process spawned unexpected child process
      PID:5040

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

    1KB

    MD5

    fbd924abc84bb73d91f2c1bb0956cb7b

    SHA1

    27a404b6f7a9055dcf7d6254bea47a1290f5a235

    SHA256

    ffac6529906c335c0ec8f79efd6b2289c59e089447c77e462f9f507f6136eaec

    SHA512

    18c35f34088a2349803c6b177becc24de8f532fcbd8f91944a79f7824004322ea461ecb179845770100b963fe91147c32a386f5c7aca684c8b4992dc9aa8ef5c

  • memory/5104-3-0x00007FFAB3C90000-0x00007FFAB3CA0000-memory.dmp

    Filesize

    64KB

  • memory/5104-11-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-15-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-10-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-16-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-12-0x00007FFAB15E0000-0x00007FFAB15F0000-memory.dmp

    Filesize

    64KB

  • memory/5104-9-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-17-0x00007FFAB15E0000-0x00007FFAB15F0000-memory.dmp

    Filesize

    64KB

  • memory/5104-7-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-6-0x00007FFAB3C90000-0x00007FFAB3CA0000-memory.dmp

    Filesize

    64KB

  • memory/5104-4-0x00007FFAB3C90000-0x00007FFAB3CA0000-memory.dmp

    Filesize

    64KB

  • memory/5104-0-0x00007FFAF3CAD000-0x00007FFAF3CAE000-memory.dmp

    Filesize

    4KB

  • memory/5104-5-0x00007FFAB3C90000-0x00007FFAB3CA0000-memory.dmp

    Filesize

    64KB

  • memory/5104-2-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-8-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-14-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-13-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-36-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-37-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-38-0x00007FFAF3CAD000-0x00007FFAF3CAE000-memory.dmp

    Filesize

    4KB

  • memory/5104-39-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-40-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-41-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-42-0x00007FFAF3C10000-0x00007FFAF3E05000-memory.dmp

    Filesize

    2.0MB

  • memory/5104-1-0x00007FFAB3C90000-0x00007FFAB3CA0000-memory.dmp

    Filesize

    64KB