Analysis

  • max time kernel
    150s
  • max time network
    150s
  • 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, 08:55

General

  • Target

    cce2048527ffdaa3366408615084a31425bd8793e75f41d9a3a05d25f74f7396.xls

  • Size

    95KB

  • MD5

    9e52aa90f3224bba98c6df773c63b77b

  • SHA1

    4de1a1453d190025b5ac77677317c4a4fb269133

  • SHA256

    cce2048527ffdaa3366408615084a31425bd8793e75f41d9a3a05d25f74f7396

  • SHA512

    ea0a7910c7459b616e5be45eea45e35628a86f5d7ce88a0caad82047e8da5d366d6b454caf6b810ff81df4fc4f2a21dc3af44a0bd5e9b25227ea2c41df2b134c

  • SSDEEP

    1536:iFKpb8rGYrMPe3q7Q0XV5xtezEsi8/dgBHuS4hcTO97v7UYdEJmMq:cKpb8rGYrMPe3q7Q0XV5xtezEsi8/dgy

Score
10/10

Malware Config

Extracted

Language
xlm4.0
Source
URLs
xlm40.dropper

https://atperson.com/campusvirtual/3aAaeSKPaURF/

xlm40.dropper

https://buffetmazzi.com.br/ckfinder/i/

xlm40.dropper

http://atici.net/c/MgEC/

xlm40.dropper

http://www.birebiregitim.net/wp-includes/f/

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\cce2048527ffdaa3366408615084a31425bd8793e75f41d9a3a05d25f74f7396.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:2300
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\soci1.ocx
      2⤵
      • Process spawned unexpected child process
      PID:3708
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\soci2.ocx
      2⤵
      • Process spawned unexpected child process
      PID:4788
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\soci3.ocx
      2⤵
      • Process spawned unexpected child process
      PID:2144
    • C:\Windows\System32\regsvr32.exe
      C:\Windows\System32\regsvr32.exe /S ..\soci4.ocx
      2⤵
      • Process spawned unexpected child process
      PID:4860

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

    23ee52c0fc0b5c77a0380155b38b59bb

    SHA1

    e2bf4f6ea35bb889d5093438cff496e9cad0ffca

    SHA256

    acee286095413b1ba460fba4b8e34001625d3e220f0c80be6004dae9881720c7

    SHA512

    c3cc98ff05fd6c2c8b1608ee71b650061ae6f5923a9065e3e3c505379c1671436cc172312cf3a4a0ecb1148f701f8cc5b89304f5d9a4e2fcafd14a2d6e1a134b

  • memory/2300-12-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-7-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-4-0x00007FF8F6550000-0x00007FF8F6560000-memory.dmp

    Filesize

    64KB

  • memory/2300-3-0x00007FF8F6550000-0x00007FF8F6560000-memory.dmp

    Filesize

    64KB

  • memory/2300-2-0x00007FF8F6550000-0x00007FF8F6560000-memory.dmp

    Filesize

    64KB

  • memory/2300-6-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-0-0x00007FF8F6550000-0x00007FF8F6560000-memory.dmp

    Filesize

    64KB

  • memory/2300-8-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-9-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-10-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-5-0x00007FF8F6550000-0x00007FF8F6560000-memory.dmp

    Filesize

    64KB

  • memory/2300-11-0x00007FF8F4420000-0x00007FF8F4430000-memory.dmp

    Filesize

    64KB

  • memory/2300-17-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-15-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-18-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-19-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-13-0x00007FF8F4420000-0x00007FF8F4430000-memory.dmp

    Filesize

    64KB

  • memory/2300-16-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-20-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-14-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-42-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-43-0x00007FF93656D000-0x00007FF93656E000-memory.dmp

    Filesize

    4KB

  • memory/2300-44-0x00007FF9364D0000-0x00007FF9366C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2300-1-0x00007FF93656D000-0x00007FF93656E000-memory.dmp

    Filesize

    4KB