Analysis

  • max time kernel
    143s
  • 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
    02-10-2024 01:18

General

  • Target

    5f7ede06fa8da808f891e29fcfc533fcab3f7e9bc02ad68d0e5b24fe006fcbe5.xls

  • Size

    640KB

  • MD5

    20e619e98752c941405d8bc0c66242b9

  • SHA1

    0320eeb4e91a97d2d78f1ddb196ff09ca7a95da0

  • SHA256

    5f7ede06fa8da808f891e29fcfc533fcab3f7e9bc02ad68d0e5b24fe006fcbe5

  • SHA512

    1a7f5cb0e1af193d9e6e07b4653648d607c4e931b32be475c0808fdd33a55a1e4257db456f8bda32f69ee09e07ba48248163127b72939eca17619110e997bdc2

  • SSDEEP

    12288:3S6nskrDE0NvKwm3HzxoO1e1ic6yWK0VceVnV2EVS7IIM:3S6nrNvIoOcl637rnV2Ey/M

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 FindShellTrayWindow 2 IoCs
  • Suspicious use of SetWindowsHookEx 12 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\5f7ede06fa8da808f891e29fcfc533fcab3f7e9bc02ad68d0e5b24fe006fcbe5.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:4180
    • C:\Windows\System32\mshta.exe
      C:\Windows\System32\mshta.exe -Embedding
      2⤵
      • Process spawned unexpected child process
      PID:2644

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

    680B

    MD5

    154e3896f0bd7da0bd1cb58dcdaae1e7

    SHA1

    bd4899b7b12317baab84a8c4b67277b7101f39bf

    SHA256

    74b416646e6d5ffd724e23d1936f11778e1f7e695e1141365507dd692870cca4

    SHA512

    c6b3ab4e9aea9592be4da1a4fa68593bb239a4e274097512077d86207a97ebb105495ff20fec6dd68c5517978b8e139cbcceab529721b6a83568a15c0f6bfc00

  • memory/2644-43-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2644-51-0x00007FF7DD050000-0x00007FF7DD058000-memory.dmp

    Filesize

    32KB

  • memory/2644-50-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2644-46-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2644-47-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2644-45-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-18-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-16-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-12-0x00007FF898EF0000-0x00007FF898F00000-memory.dmp

    Filesize

    64KB

  • memory/4180-14-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-15-0x00007FF898EF0000-0x00007FF898F00000-memory.dmp

    Filesize

    64KB

  • memory/4180-19-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-20-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-2-0x00007FF89B850000-0x00007FF89B860000-memory.dmp

    Filesize

    64KB

  • memory/4180-22-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-21-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-17-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-13-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-8-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-7-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-4-0x00007FF89B850000-0x00007FF89B860000-memory.dmp

    Filesize

    64KB

  • memory/4180-3-0x00007FF8DB86D000-0x00007FF8DB86E000-memory.dmp

    Filesize

    4KB

  • memory/4180-11-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-10-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-9-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-6-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-49-0x00007FF8DB7D0000-0x00007FF8DB9C5000-memory.dmp

    Filesize

    2.0MB

  • memory/4180-5-0x00007FF89B850000-0x00007FF89B860000-memory.dmp

    Filesize

    64KB

  • memory/4180-0-0x00007FF89B850000-0x00007FF89B860000-memory.dmp

    Filesize

    64KB

  • memory/4180-1-0x00007FF89B850000-0x00007FF89B860000-memory.dmp

    Filesize

    64KB