Analysis

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

    arch:x64arch:x86image:win10v2004-20241007-enlocale:en-usos:windows10-2004-x64system
  • submitted
    04-11-2024 06:58

General

  • Target

    PaymentAdvice-RefA22D4YdWsbE4.xla.xls

  • Size

    937KB

  • MD5

    b01b76c877321d03dab23c4d1bb26e48

  • SHA1

    faf698726f93f31fc1fcab31e8942d690220fa10

  • SHA256

    421895be443167f773741e1681d27ba2052fbef90d4def330cadb3206dbd651c

  • SHA512

    6756a5eefa442726525208796c7406146407be1a779655a647cdd3caa38a5c761848caf5a978e4cd612713aaef9307221411372859dffa82c860d723b307fc64

  • SSDEEP

    12288:2UXN9WeWy3aJwF1E3Zjy5dbHsu6KGsW+DYavtKVUgGw6M6ozBdUepzBf88SKe:fusaGF1EpyYu67sdDNVK+f9oTptaK

Score
10/10

Malware Config

Signatures

  • Process spawned unexpected child process 1 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 SetWindowsHookEx 8 IoCs
  • Suspicious use of WriteProcessMemory 2 IoCs
  • Uses Task Scheduler COM API 1 TTPs

    The Task Scheduler COM API can be used to schedule applications to run on boot or at set times.

  • Uses Volume Shadow Copy WMI provider

    The Volume Shadow Copy service is used to manage backups/snapshots.

  • Uses Volume Shadow Copy service COM API

    The Volume Shadow Copy service is used to manage backups/snapshots.

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\PaymentAdvice-RefA22D4YdWsbE4.xla.xls"
    1⤵
    • Checks processor information in registry
    • Enumerates system info in registry
    • Suspicious behavior: AddClipboardFormatListener
    • Suspicious use of SetWindowsHookEx
    • Suspicious use of WriteProcessMemory
    PID:3080
    • C:\Windows\System32\mshta.exe
      C:\Windows\System32\mshta.exe -Embedding
      2⤵
      • Process spawned unexpected child process
      PID:1872

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

    832103e8594d85627d8e52b30497fc93

    SHA1

    b77a39e32a3cd6993aef4537726a5f250333f6c6

    SHA256

    62d7bb75f3a0bfe3cc8b82e91731acfd3b6b29968cba52d511090475705af344

    SHA512

    e2a75374f026ea05e21176703dfee28272f6f1a1bc6fa5363c3634563b52de9f4752dbf2e867e9daf91a78c705fdfc560f51988cf3193a4c74e90707e571f8a3

  • memory/1872-40-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/1872-55-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/1872-54-0x00007FF63F170000-0x00007FF63F178000-memory.dmp

    Filesize

    32KB

  • memory/1872-46-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/1872-45-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-9-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-21-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-0-0x00007FFBD0C50000-0x00007FFBD0C60000-memory.dmp

    Filesize

    64KB

  • memory/3080-10-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-11-0x00007FFBCEA70000-0x00007FFBCEA80000-memory.dmp

    Filesize

    64KB

  • memory/3080-12-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-8-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-16-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-15-0x00007FFBCEA70000-0x00007FFBCEA80000-memory.dmp

    Filesize

    64KB

  • memory/3080-18-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-17-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-20-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-19-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-7-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-22-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-14-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-13-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-6-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-4-0x00007FFBD0C50000-0x00007FFBD0C60000-memory.dmp

    Filesize

    64KB

  • memory/3080-5-0x00007FFBD0C50000-0x00007FFBD0C60000-memory.dmp

    Filesize

    64KB

  • memory/3080-48-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-49-0x00007FFC10C6D000-0x00007FFC10C6E000-memory.dmp

    Filesize

    4KB

  • memory/3080-50-0x00007FFC10BD0000-0x00007FFC10DC5000-memory.dmp

    Filesize

    2.0MB

  • memory/3080-2-0x00007FFBD0C50000-0x00007FFBD0C60000-memory.dmp

    Filesize

    64KB

  • memory/3080-3-0x00007FFBD0C50000-0x00007FFBD0C60000-memory.dmp

    Filesize

    64KB

  • memory/3080-1-0x00007FFC10C6D000-0x00007FFC10C6E000-memory.dmp

    Filesize

    4KB