Analysis

  • max time kernel
    134s
  • max time network
    140s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20250314-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20250314-enlocale:en-usos:windows10-2004-x64system
  • submitted
    10/04/2025, 17:36

General

  • Target

    $TEMP/Surrey.doc

  • Size

    86KB

  • MD5

    2562d60d0ce8500a33f91910eb602e72

  • SHA1

    6f54357ee23017093e9f6e23053fb5bb6c714487

  • SHA256

    175779c0f23e28a62fd2b7e9f7a04756b671292dd19ef3e074efe1f90aa6e216

  • SHA512

    677607ecd8c411abee75c040a42cfbce6bfd7e9b01cba2f8635eac2d76326b39a89635b6d2676a386b4ffbe86aeea91831c931ba2f14ee83661a8e89497a9670

  • SSDEEP

    1536:IYa7jMjJ9gICkQTdY8nRlENdlDIUWUqRzrKO0FP8Ip9ypPbKT4VKW:IYcQJ9gG+XRl2D4HKO0VRepmmx

Score
1/10

Malware Config

Signatures

  • 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 2 IoCs
  • Suspicious use of SetWindowsHookEx 16 IoCs

Processes

  • C:\Program Files\Microsoft Office\Root\Office16\WINWORD.EXE
    "C:\Program Files\Microsoft Office\Root\Office16\WINWORD.EXE" /n "C:\Users\Admin\AppData\Local\Temp\$TEMP\Surrey.doc" /o ""
    1⤵
    • Checks processor information in registry
    • Enumerates system info in registry
    • Suspicious behavior: AddClipboardFormatListener
    • Suspicious use of SetWindowsHookEx
    PID:3800

Network

MITRE ATT&CK Enterprise v16

Replay Monitor

Loading Replay Monitor...

Downloads

  • memory/3800-0-0x00007FF8E8270000-0x00007FF8E8280000-memory.dmp

    Filesize

    64KB

  • memory/3800-2-0x00007FF8E8270000-0x00007FF8E8280000-memory.dmp

    Filesize

    64KB

  • memory/3800-1-0x00007FF92828D000-0x00007FF92828E000-memory.dmp

    Filesize

    4KB

  • memory/3800-3-0x00007FF8E8270000-0x00007FF8E8280000-memory.dmp

    Filesize

    64KB

  • memory/3800-5-0x00007FF8E8270000-0x00007FF8E8280000-memory.dmp

    Filesize

    64KB

  • memory/3800-4-0x00007FF8E8270000-0x00007FF8E8280000-memory.dmp

    Filesize

    64KB

  • memory/3800-8-0x00007FF9281F0000-0x00007FF9283E5000-memory.dmp

    Filesize

    2.0MB

  • memory/3800-9-0x00007FF9281F0000-0x00007FF9283E5000-memory.dmp

    Filesize

    2.0MB

  • memory/3800-12-0x00007FF9281F0000-0x00007FF9283E5000-memory.dmp

    Filesize

    2.0MB

  • memory/3800-14-0x00007FF9281F0000-0x00007FF9283E5000-memory.dmp

    Filesize

    2.0MB

  • memory/3800-16-0x00007FF8E5960000-0x00007FF8E5970000-memory.dmp

    Filesize

    64KB

  • memory/3800-15-0x00007FF9281F0000-0x00007FF9283E5000-memory.dmp

    Filesize

    2.0MB

  • memory/3800-13-0x00007FF9281F0000-0x00007FF9283E5000-memory.dmp

    Filesize

    2.0MB

  • memory/3800-11-0x00007FF9281F0000-0x00007FF9283E5000-memory.dmp

    Filesize

    2.0MB

  • memory/3800-10-0x00007FF9281F0000-0x00007FF9283E5000-memory.dmp

    Filesize

    2.0MB

  • memory/3800-7-0x00007FF9281F0000-0x00007FF9283E5000-memory.dmp

    Filesize

    2.0MB

  • memory/3800-6-0x00007FF9281F0000-0x00007FF9283E5000-memory.dmp

    Filesize

    2.0MB

  • memory/3800-17-0x00007FF8E5960000-0x00007FF8E5970000-memory.dmp

    Filesize

    64KB

  • memory/3800-29-0x00007FF9281F0000-0x00007FF9283E5000-memory.dmp

    Filesize

    2.0MB

  • memory/3800-30-0x00007FF92828D000-0x00007FF92828E000-memory.dmp

    Filesize

    4KB

  • memory/3800-31-0x00007FF9281F0000-0x00007FF9283E5000-memory.dmp

    Filesize

    2.0MB