Analysis

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

    arch:x64arch:x86image:win10v2004-20241007-enlocale:en-usos:windows10-2004-x64system
  • submitted
    19-11-2024 08:49

General

  • Target

    19112024_0849_18112024_PO-000041492.xls

  • Size

    1.1MB

  • MD5

    f69d18b27ddddb4274a97434c6a01ae2

  • SHA1

    79a2cf394e8fe22341922a6490e9d58a87e2f748

  • SHA256

    555c9fab8b1c2180ec0c140d7ef7a072d3848661e47051b4dda5de40a61465b7

  • SHA512

    32acd768dc2ec5095216e946f8cd119174ee252d4691d4816f91881a3c5439db68feffe24bc85a16dcdf9caf3d53b82fa89f35b89540148e8c862664c851a77c

  • SSDEEP

    24576:6uq9PLiijE2Z5Z2amowshXCdQtF84LJQohVsx7ACKg0q9JfCazDVNPCTy2vo:6uEPLiij7Z5ZKowsAsFjLJQohVKEg0qR

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

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

    3KB

    MD5

    aec0871fd8096f0bb7d3cd4f2623c5c9

    SHA1

    a294aa235e2620c3ab5a16ff168e911585ce2680

    SHA256

    16b85a23b0efe2543b8f122e11ee554b31f72384509c4084b2c89cdedca413b3

    SHA512

    8ab42c6943adf65fc28cd48e64cb18811cca2e7d6a34708c77a31db10516508f7153bca35048fa7ecc851e715bd2e4b5354328ebd841f644caa3cdd2a66049ea

  • memory/2168-39-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2168-53-0x00007FF7AB920000-0x00007FF7AB928000-memory.dmp

    Filesize

    32KB

  • memory/2168-52-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2168-45-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2168-46-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2168-42-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-14-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-20-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-12-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-13-0x00007FFB37A90000-0x00007FFB37AA0000-memory.dmp

    Filesize

    64KB

  • memory/2668-11-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-7-0x00007FFB39C30000-0x00007FFB39C40000-memory.dmp

    Filesize

    64KB

  • memory/2668-6-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-0-0x00007FFB39C30000-0x00007FFB39C40000-memory.dmp

    Filesize

    64KB

  • memory/2668-15-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-17-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-16-0x00007FFB37A90000-0x00007FFB37AA0000-memory.dmp

    Filesize

    64KB

  • memory/2668-10-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-19-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-21-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-18-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-9-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-8-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-4-0x00007FFB39C30000-0x00007FFB39C40000-memory.dmp

    Filesize

    64KB

  • memory/2668-5-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-51-0x00007FFB79BB0000-0x00007FFB79DA5000-memory.dmp

    Filesize

    2.0MB

  • memory/2668-1-0x00007FFB39C30000-0x00007FFB39C40000-memory.dmp

    Filesize

    64KB

  • memory/2668-2-0x00007FFB39C30000-0x00007FFB39C40000-memory.dmp

    Filesize

    64KB

  • memory/2668-3-0x00007FFB79C4D000-0x00007FFB79C4E000-memory.dmp

    Filesize

    4KB