Analysis

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

    arch:x64arch:x86image:win10v2004-20241007-enlocale:en-usos:windows10-2004-x64system
  • submitted
    09-12-2024 21:05

General

  • Target

    73bcfd130533d37048c4198fa57158ff30c005bd1b08f7f06afe067e555e5096.doc

  • Size

    446KB

  • MD5

    d8c4fa8f0039b50323e326878a2e8f44

  • SHA1

    2630a910c038b044eb0fa987c76b4481d09a309b

  • SHA256

    73bcfd130533d37048c4198fa57158ff30c005bd1b08f7f06afe067e555e5096

  • SHA512

    97f61388e0c40d1520e7a26601ae5ec806ba02cdbbfa47ea4d2d915fb37956feff1dc7e8c7cd571321055ec79117072ac43a74c6dc5ebe233a0fb24ca23ca241

  • SSDEEP

    6144:VYtw1e3FMH7ujugUPfZU4aIyAYyN5VIHG/epSr8/FibeUxYT8Z37Sx0eDGk7u:fy0

Malware Config

Extracted

Family

metasploit

Version

windows/reverse_tcp

C2

163.177.122.50:443

Signatures

  • MetaSploit

    Detected malicious payload which is part of the Metasploit Framework, likely generated with msfvenom or similar.

  • Metasploit family
  • Process spawned suspicious child process 1 IoCs

    This child process is typically not spawned unless (for example) the parent process crashes. This typically indicates the parent process was unsuccessfully compromised.

  • Checks processor information in registry 2 TTPs 6 IoCs

    Processor information is often read in order to detect sandboxing environments.

  • Enumerates system info in registry 2 TTPs 5 IoCs
  • Suspicious behavior: AddClipboardFormatListener 2 IoCs
  • Suspicious behavior: EnumeratesProcesses 4 IoCs
  • Suspicious use of SetWindowsHookEx 4 IoCs
  • Suspicious use of WriteProcessMemory 4 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\73bcfd130533d37048c4198fa57158ff30c005bd1b08f7f06afe067e555e5096.doc" /o ""
    1⤵
    • Checks processor information in registry
    • Enumerates system info in registry
    • Suspicious behavior: AddClipboardFormatListener
    • Suspicious behavior: EnumeratesProcesses
    • Suspicious use of SetWindowsHookEx
    • Suspicious use of WriteProcessMemory
    PID:1600
    • C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\DW\DW20.EXE
      "C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\DW\DW20.EXE" -x -s 4568
      2⤵
      • Process spawned suspicious child process
      • Suspicious use of WriteProcessMemory
      PID:212
      • C:\Windows\system32\dwwin.exe
        C:\Windows\system32\dwwin.exe -x -s 4568
        3⤵
        • Checks processor information in registry
        • Enumerates system info in registry
        PID:552

Network

MITRE ATT&CK Enterprise v15

Replay Monitor

Loading Replay Monitor...

Downloads

  • memory/212-34-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/212-60-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/212-56-0x00007FFF3F3F0000-0x00007FFF3F400000-memory.dmp

    Filesize

    64KB

  • memory/212-57-0x00007FFF3F3F0000-0x00007FFF3F400000-memory.dmp

    Filesize

    64KB

  • memory/212-58-0x00007FFF3F3F0000-0x00007FFF3F400000-memory.dmp

    Filesize

    64KB

  • memory/212-59-0x00007FFF3F3F0000-0x00007FFF3F400000-memory.dmp

    Filesize

    64KB

  • memory/212-37-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/212-38-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-14-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-27-0x0000027E25BF0000-0x0000027E25BF1000-memory.dmp

    Filesize

    4KB

  • memory/1600-16-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-17-0x00007FFF3CA90000-0x00007FFF3CAA0000-memory.dmp

    Filesize

    64KB

  • memory/1600-13-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-12-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-11-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-6-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-5-0x00007FFF3F3F0000-0x00007FFF3F400000-memory.dmp

    Filesize

    64KB

  • memory/1600-8-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-18-0x00007FFF3CA90000-0x00007FFF3CAA0000-memory.dmp

    Filesize

    64KB

  • memory/1600-15-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-28-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-29-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-30-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-0-0x00007FFF3F3F0000-0x00007FFF3F400000-memory.dmp

    Filesize

    64KB

  • memory/1600-9-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-10-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-7-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB

  • memory/1600-2-0x00007FFF3F3F0000-0x00007FFF3F400000-memory.dmp

    Filesize

    64KB

  • memory/1600-3-0x00007FFF3F3F0000-0x00007FFF3F400000-memory.dmp

    Filesize

    64KB

  • memory/1600-4-0x00007FFF3F3F0000-0x00007FFF3F400000-memory.dmp

    Filesize

    64KB

  • memory/1600-1-0x00007FFF7F40D000-0x00007FFF7F40E000-memory.dmp

    Filesize

    4KB

  • memory/1600-62-0x00007FFF7F370000-0x00007FFF7F565000-memory.dmp

    Filesize

    2.0MB