Analysis

  • max time kernel
    133s
  • max time network
    156s
  • 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, 12:50

General

  • Target

    Outstanding INVOICE DTQC-158641-173 04-07-2022_1402.xls

  • Size

    95KB

  • MD5

    fda9b005a725d9f698e24b16c3b0eb2a

  • SHA1

    a3bbffdd39f23b08035496f8d394354384e2397f

  • SHA256

    6fc29cee6754fe79ad16a2d1df7eccd43798c9a1bf4dad634cbd7697700c154e

  • SHA512

    169d4198776efb06b740f99d113825e446b522cb720d728029a8c1eb7594c7cdb6a30c645359ac9ac5579711870cde845c0e5b002c21c67a5bca2e3bae104703

  • SSDEEP

    1536:iFKpb8rGYrMPe3q7Q0XV5xtezEsi8/dg0yHuS4hcTO97v7UYdEJmA/:cKpb8rGYrMPe3q7Q0XV5xtezEsi8/dgH

Score
10/10

Malware Config

Extracted

Language
xlm4.0
Source
URLs
xlm40.dropper

https://f5ajans.com/merthel/vvWRK/KVVGB6o7SPoorfaI/

xlm40.dropper

http://emett.com/images/kk2l4zoRKwv2vIEK/

xlm40.dropper

https://www.duinrand-s.nl/Nieuws/S9Y8DumfrBU1r5unO/

xlm40.dropper

http://galileuconcursos.com.br/wp-admin/Pt8VGg/

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\Outstanding INVOICE DTQC-158641-173 04-07-2022_1402.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:2108
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\uoya1.ocx
      2⤵
      • Process spawned unexpected child process
      PID:4708
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\uoya2.ocx
      2⤵
      • Process spawned unexpected child process
      PID:2076
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\uoya3.ocx
      2⤵
      • Process spawned unexpected child process
      PID:4892
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\uoya4.ocx
      2⤵
      • Process spawned unexpected child process
      PID:1672

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

    bd72678f1b91b6786636b31d58e5c2e7

    SHA1

    ca0a9ae397153ce2d7bd723920b0971fb176a035

    SHA256

    038fb0a28575e7364c7a4796bf19086ef98e51b74bef4fadb9cde22b4ad38d3f

    SHA512

    dd00268a4231bb5272b4388dd33d5cea79edd3b2499a7ba87bf8b728bc1c8e1815b6931e38d48f1f91795ca6c70e40e0a90c7ba86df10f9a6625172ba2549b17

  • C:\Users\Admin\uoya3.ocx

    Filesize

    33KB

    MD5

    38e58d5fa77dbcc313c91a0a49dc4ba8

    SHA1

    1029087462def3dbd90041a43283f3917dc9da1c

    SHA256

    a32245acdb3894736baf5f9041ae278c766957b5ebe1f08da0d2249165b26717

    SHA512

    fecf9a0006da91b27296b160798cfe0dceee41b5d213f35c0a0193157d67b98d1aef2e0322caecf3df8c1eb5b0bb97794beded32ad494e09b5001cfe5423c516

  • memory/2108-3-0x00007FFF360AD000-0x00007FFF360AE000-memory.dmp

    Filesize

    4KB

  • memory/2108-13-0x00007FFEF3DF0000-0x00007FFEF3E00000-memory.dmp

    Filesize

    64KB

  • memory/2108-10-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-8-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-7-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-6-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-5-0x00007FFEF6090000-0x00007FFEF60A0000-memory.dmp

    Filesize

    64KB

  • memory/2108-11-0x00007FFEF3DF0000-0x00007FFEF3E00000-memory.dmp

    Filesize

    64KB

  • memory/2108-9-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-14-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-0-0x00007FFEF6090000-0x00007FFEF60A0000-memory.dmp

    Filesize

    64KB

  • memory/2108-4-0x00007FFEF6090000-0x00007FFEF60A0000-memory.dmp

    Filesize

    64KB

  • memory/2108-12-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-15-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-17-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-18-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-16-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-20-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-19-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-39-0x00007FFF36010000-0x00007FFF36205000-memory.dmp

    Filesize

    2.0MB

  • memory/2108-1-0x00007FFEF6090000-0x00007FFEF60A0000-memory.dmp

    Filesize

    64KB

  • memory/2108-2-0x00007FFEF6090000-0x00007FFEF60A0000-memory.dmp

    Filesize

    64KB