Analysis

  • max time kernel
    149s
  • 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
    29-10-2024 02:46

General

  • Target

    a563257161e5c3947e4ea5669e1ef5eafbe67d5049816de47313ada6f299ac10.xls

  • Size

    98KB

  • MD5

    b8fe6365e4a55cb70d0b9c457a7a7099

  • SHA1

    da353f9118f9d6c3a6eeea1891a3b8e0e89742d1

  • SHA256

    a563257161e5c3947e4ea5669e1ef5eafbe67d5049816de47313ada6f299ac10

  • SHA512

    cc884090cc6a883f58d85940c236e73faa92f27d3a501023264ab844028c75a3dac601218f17f52df46729778e8078bb4a52950a30f4e76b4d18de10b94f1f22

  • SSDEEP

    1536:4iqHy1S6F8b2SQrEkawpoXIonlwQMlUD5/VHGFht5mGs7Xh2ROvHt0ydYfki:QeFHrE2sIonlwQMl65/VmLIx24m

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

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

    4KB

    MD5

    5ba6ac16df6a71a9f007165558e87203

    SHA1

    684bc8a5706f8408279b86e9bcb08d33b3c89b26

    SHA256

    9e422099987bc88d7b798db1b580ce777928611669b903f9e5c348eae13c6fd5

    SHA512

    0eba0d2303014f640d3b20af5286f213f11119e5d9170e72a16dbffa71eaf040d15543a4e50fdb7f97e771b420a6a2d48b0039726d7faa7ea41e24e194634aa3

  • memory/1744-15-0x00007FF839DA0000-0x00007FF839DB0000-memory.dmp

    Filesize

    64KB

  • memory/1744-5-0x00007FF83C3F0000-0x00007FF83C400000-memory.dmp

    Filesize

    64KB

  • memory/1744-17-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-4-0x00007FF83C3F0000-0x00007FF83C400000-memory.dmp

    Filesize

    64KB

  • memory/1744-18-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-7-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-9-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-8-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-10-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-12-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-13-0x00007FF839DA0000-0x00007FF839DB0000-memory.dmp

    Filesize

    64KB

  • memory/1744-20-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-6-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-0-0x00007FF83C3F0000-0x00007FF83C400000-memory.dmp

    Filesize

    64KB

  • memory/1744-2-0x00007FF83C3F0000-0x00007FF83C400000-memory.dmp

    Filesize

    64KB

  • memory/1744-1-0x00007FF87C40D000-0x00007FF87C40E000-memory.dmp

    Filesize

    4KB

  • memory/1744-11-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-19-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-16-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-14-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/1744-3-0x00007FF83C3F0000-0x00007FF83C400000-memory.dmp

    Filesize

    64KB

  • memory/1744-52-0x00007FF87C40D000-0x00007FF87C40E000-memory.dmp

    Filesize

    4KB

  • memory/1744-51-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/5000-46-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/5000-45-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/5000-42-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/5000-56-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB

  • memory/5000-57-0x00007FF6F6FF0000-0x00007FF6F6FF8000-memory.dmp

    Filesize

    32KB

  • memory/5000-43-0x00007FF87C370000-0x00007FF87C565000-memory.dmp

    Filesize

    2.0MB