Analysis

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

General

  • Target

    a41dfd112fed7df825f4863b94e168d7.xls

  • Size

    94KB

  • MD5

    a41dfd112fed7df825f4863b94e168d7

  • SHA1

    bd249e289dc3189a3709dd038c06ae428fdbf3f6

  • SHA256

    487ec96355ff0dcffde022991ef51d52afdaab2901a80c3fe2a25b3a56dcbc7d

  • SHA512

    df0993c926a3e11923d0161d6c7f5f30280fc862424ac2d79c20e53df95845848661a55484aa122ccb4b772d58b4b2237aa7d594b6f827afe8d8090f5487a4ee

  • SSDEEP

    1536:NFKpb8rGYrMPe3q7Q0XV5xtezEsi8/dgiHuS4hcTO97v7UYdEJmFCu:3Kpb8rGYrMPe3q7Q0XV5xtezEsi8/dgj

Score
10/10

Malware Config

Extracted

Language
xlm4.0
Source
URLs
xlm40.dropper

https://ewingconsulting.com/wp-includes/1sqrshC/

xlm40.dropper

http://www.llev.com.br/app/W2ehSSGWXTBpOf/

xlm40.dropper

http://digital21.cl/genchile/Pp1LDfwHR0IJPWHpq3R/

xlm40.dropper

http://nellydwiputri.co.id/images/lZfuoNe2vyr/

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\a41dfd112fed7df825f4863b94e168d7.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:4964
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\uoya1.ocx
      2⤵
      • Process spawned unexpected child process
      PID:4296
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\uoya2.ocx
      2⤵
      • Process spawned unexpected child process
      PID:2736
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\uoya3.ocx
      2⤵
      • Process spawned unexpected child process
      PID:1248
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\uoya4.ocx
      2⤵
      • Process spawned unexpected child process
      PID:4568

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

    adcb44c7630c7edcde63453d0524f5d2

    SHA1

    c33e931c633f514ab7642aaca55114b2acffeb8f

    SHA256

    4dbb12a73e6e69cbad97ae1fa0a102d18758bb264dc559251c62a0992e225b35

    SHA512

    e6dd92cc2488b19481e70023a2a390a9a5c645bdec7f4f9ea68091f4f7df6774120792fa02932040f402b3594f57f142a3d26867980726135f92e23493cd878b

  • C:\Users\Admin\uoya1.ocx

    Filesize

    114B

    MD5

    e89f75f918dbdcee28604d4e09dd71d7

    SHA1

    f9d9055e9878723a12063b47d4a1a5f58c3eb1e9

    SHA256

    6dc9c7fc93bb488bb0520a6c780a8d3c0fb5486a4711aca49b4c53fac7393023

    SHA512

    8df0ab2e3679b64a6174deff4259ae5680f88e3ae307e0ea2dfff88ec4ba14f3477c9fe3a5aa5da3a8e857601170a5108ed75f6d6975958ac7a314e4a336aed0

  • memory/4964-14-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-4-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-7-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-8-0x00007FFF81090000-0x00007FFF810A0000-memory.dmp

    Filesize

    64KB

  • memory/4964-10-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-9-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-6-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-16-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-15-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-13-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-3-0x00007FFF81090000-0x00007FFF810A0000-memory.dmp

    Filesize

    64KB

  • memory/4964-0-0x00007FFF81090000-0x00007FFF810A0000-memory.dmp

    Filesize

    64KB

  • memory/4964-5-0x00007FFF81090000-0x00007FFF810A0000-memory.dmp

    Filesize

    64KB

  • memory/4964-17-0x00007FFF7EEA0000-0x00007FFF7EEB0000-memory.dmp

    Filesize

    64KB

  • memory/4964-12-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-11-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-18-0x00007FFF7EEA0000-0x00007FFF7EEB0000-memory.dmp

    Filesize

    64KB

  • memory/4964-1-0x00007FFFC10AD000-0x00007FFFC10AE000-memory.dmp

    Filesize

    4KB

  • memory/4964-56-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-57-0x00007FFFC10AD000-0x00007FFFC10AE000-memory.dmp

    Filesize

    4KB

  • memory/4964-58-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-59-0x00007FFFC1010000-0x00007FFFC1205000-memory.dmp

    Filesize

    2.0MB

  • memory/4964-2-0x00007FFF81090000-0x00007FFF810A0000-memory.dmp

    Filesize

    64KB