Analysis

  • max time kernel
    143s
  • max time network
    151s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20230915-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20230915-enlocale:en-usos:windows10-2004-x64system
  • submitted
    08/10/2023, 18:40

General

  • Target

    0363318de42db42dfff101f3b57f10f7709bca44ad0e982a4413c2ce9171d376.exe

  • Size

    956KB

  • MD5

    ee8ffb4e6b2b64378ad5ffc1693df200

  • SHA1

    f889002ddbc207eb35a20fc24af7aa8165825fdf

  • SHA256

    0363318de42db42dfff101f3b57f10f7709bca44ad0e982a4413c2ce9171d376

  • SHA512

    e9c1eed5e8d786d695b20144d6cc6f410e6e5f04b8b203d06655becc1b868f40b14281dc80b098e3943cb42423ae822ebbc7d6fec811ff20648c293e7d1cc75b

  • SSDEEP

    24576:dK7uKIjylbQ21b/G+BWk31DVtXa41MqyCF:ATH/GQ31v14CF

Score
3/10

Malware Config

Signatures

  • Program crash 1 IoCs
  • Suspicious use of SetWindowsHookEx 2 IoCs

Processes

  • C:\Users\Admin\AppData\Local\Temp\0363318de42db42dfff101f3b57f10f7709bca44ad0e982a4413c2ce9171d376.exe
    "C:\Users\Admin\AppData\Local\Temp\0363318de42db42dfff101f3b57f10f7709bca44ad0e982a4413c2ce9171d376.exe"
    1⤵
    • Suspicious use of SetWindowsHookEx
    PID:4252
    • C:\Windows\SysWOW64\WerFault.exe
      C:\Windows\SysWOW64\WerFault.exe -u -p 4252 -s 844
      2⤵
      • Program crash
      PID:3260
  • C:\Windows\SysWOW64\WerFault.exe
    C:\Windows\SysWOW64\WerFault.exe -pss -s 416 -p 4252 -ip 4252
    1⤵
      PID:1832

    Network

    MITRE ATT&CK Matrix

    Replay Monitor

    Loading Replay Monitor...

    Downloads

    • memory/4252-0-0x0000000000400000-0x0000000000516000-memory.dmp

      Filesize

      1.1MB

    • memory/4252-1-0x0000000000400000-0x0000000000516000-memory.dmp

      Filesize

      1.1MB