Analysis

  • max time kernel
    149s
  • max time network
    150s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20231215-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20231215-enlocale:en-usos:windows10-2004-x64system
  • submitted
    14-01-2024 01:15

General

  • Target

    kopje.rtf

  • Size

    1.8MB

  • MD5

    e5b1517921a1c423589c034caf44de00

  • SHA1

    c8492bdd9a71a6bcf51179bfdcddcfa4ffb4388c

  • SHA256

    d40bff228e6e7e91ec7fb7a35a390bff736758ea89260d6c55bc0aca204effc5

  • SHA512

    3538938e77cb834b945f787f0880dfc771552bdd45296862cfaa2f2f673fd12779a2a1357327321f80e5786adea3dd63c619f89aa79b6c98433d3efad14b9c29

  • SSDEEP

    49152:ObpiQjMczQhnGLnc2fgqSZWIig/+spaBw:O9AThnM1fgVZWIFpaBw

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 17 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\kopje.rtf" /o ""
    1⤵
    • Checks processor information in registry
    • Enumerates system info in registry
    • Suspicious behavior: AddClipboardFormatListener
    • Suspicious use of SetWindowsHookEx
    PID:4368

Network

MITRE ATT&CK Enterprise v15

Replay Monitor

Loading Replay Monitor...

Downloads

  • memory/4368-0-0x00007FFF19E50000-0x00007FFF19E60000-memory.dmp

    Filesize

    64KB

  • memory/4368-1-0x00007FFF19E50000-0x00007FFF19E60000-memory.dmp

    Filesize

    64KB

  • memory/4368-2-0x00007FFF19E50000-0x00007FFF19E60000-memory.dmp

    Filesize

    64KB

  • memory/4368-3-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-4-0x00007FFF19E50000-0x00007FFF19E60000-memory.dmp

    Filesize

    64KB

  • memory/4368-6-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-5-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-7-0x00007FFF19E50000-0x00007FFF19E60000-memory.dmp

    Filesize

    64KB

  • memory/4368-8-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-9-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-10-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-11-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-13-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-12-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-14-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-16-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-18-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-19-0x00007FFF17DF0000-0x00007FFF17E00000-memory.dmp

    Filesize

    64KB

  • memory/4368-20-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-17-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-15-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-21-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB

  • memory/4368-22-0x00007FFF17DF0000-0x00007FFF17E00000-memory.dmp

    Filesize

    64KB

  • memory/4368-25-0x00007FFF59DD0000-0x00007FFF59FC5000-memory.dmp

    Filesize

    2.0MB