Analysis

  • max time kernel
    293s
  • max time network
    278s
  • 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 15:55

General

  • Target

    29102024_1555_29102024_Payment slip.xls

  • Size

    1.2MB

  • MD5

    fb16f7b0fbcb2ae5d3b185392e4543a5

  • SHA1

    f5e0e6247b2fd7ec74fc687ba0f63d8c05cc3fe0

  • SHA256

    8f4cb3b0aaf0bdbbcc6d080385fab14ae0cf71d8e46770902ade7f5e4099b5da

  • SHA512

    f20b0cd4b5030f517997783caa172e5415bfaefd38cf791c983948ae3a20967fe16840e283e6e4833f0d73d0ba7513f49e212f0bd6db7f1d9a1bf8e473668bb5

  • SSDEEP

    24576:G1852p5l2JsykgMpRptnPskUcZnujf9VYdHk5Xqx5Q:G1O2p5l2oFpB0kUcIf9naT

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\29102024_1555_29102024_Payment slip.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:3424
    • C:\Windows\System32\mshta.exe
      C:\Windows\System32\mshta.exe -Embedding
      2⤵
      • Process spawned unexpected child process
      PID:2884

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

    e8770aa0a83eb4c95693aca143a6e424

    SHA1

    0a021c01d50399d64613723a5b7cf02c697eae56

    SHA256

    bd3b767340f0d742cfae45bdf64568a161de41e34759b6d379fbf26211910439

    SHA512

    d67f54cc0f2e38c9a9d6f01399c59f3020b5aea95d7ad8cca4488f32c1cbc551c25105789c0c90df001ae99313eb46d32d350177d53551ebadcf1924eb7be1af

  • memory/2884-44-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2884-54-0x00007FF65FE60000-0x00007FF65FE68000-memory.dmp

    Filesize

    32KB

  • memory/2884-53-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2884-47-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2884-46-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/2884-40-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-10-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-19-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-8-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-11-0x00007FF8AA2F0000-0x00007FF8AA300000-memory.dmp

    Filesize

    64KB

  • memory/3424-6-0x00007FF8AC350000-0x00007FF8AC360000-memory.dmp

    Filesize

    64KB

  • memory/3424-12-0x00007FF8AA2F0000-0x00007FF8AA300000-memory.dmp

    Filesize

    64KB

  • memory/3424-13-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-15-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-14-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-17-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-20-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-9-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-18-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-16-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-0-0x00007FF8AC350000-0x00007FF8AC360000-memory.dmp

    Filesize

    64KB

  • memory/3424-7-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-5-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-1-0x00007FF8AC350000-0x00007FF8AC360000-memory.dmp

    Filesize

    64KB

  • memory/3424-49-0x00007FF8EC2D0000-0x00007FF8EC4C5000-memory.dmp

    Filesize

    2.0MB

  • memory/3424-2-0x00007FF8AC350000-0x00007FF8AC360000-memory.dmp

    Filesize

    64KB

  • memory/3424-4-0x00007FF8AC350000-0x00007FF8AC360000-memory.dmp

    Filesize

    64KB

  • memory/3424-3-0x00007FF8EC36D000-0x00007FF8EC36E000-memory.dmp

    Filesize

    4KB