Analysis

  • max time kernel
    133s
  • 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
    14/04/2025, 13:48

General

  • Target

    virusshare/2/VirusShare_3f0b1eed4b7b9ae05fab4d949843f103.doc

  • Size

    35KB

  • MD5

    3f0b1eed4b7b9ae05fab4d949843f103

  • SHA1

    e5b9fa0a23f337adae93ed4e8fcd1e9d9db4acba

  • SHA256

    ce21d34bafe338effb8f619936f057084cb45743fce884a1465966d8523a00a8

  • SHA512

    292183a9d0b3e5759453a43bcf34b8b1d09d09523687bfab090dd740a5c70169938904949b1c5a025b40082898dc3ec240ad2ec788b66f256efe5a041f774740

  • SSDEEP

    384:3+WbqwPv/ETzbVwNY/+TU5lHizK+BS3DzxW8M2GzraAzVCIXh3aM:OWbqm/EvZwO2TUrEQDtI2G31lX5

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\virusshare\2\VirusShare_3f0b1eed4b7b9ae05fab4d949843f103.doc" /o ""
    1⤵
    • Checks processor information in registry
    • Enumerates system info in registry
    • Suspicious behavior: AddClipboardFormatListener
    • Suspicious use of SetWindowsHookEx
    PID:3040

Network

MITRE ATT&CK Enterprise v16

Replay Monitor

Loading Replay Monitor...

Downloads

  • memory/3040-0-0x00007FF926E2D000-0x00007FF926E2E000-memory.dmp

    Filesize

    4KB

  • memory/3040-3-0x00007FF8E6E10000-0x00007FF8E6E20000-memory.dmp

    Filesize

    64KB

  • memory/3040-2-0x00007FF8E6E10000-0x00007FF8E6E20000-memory.dmp

    Filesize

    64KB

  • memory/3040-1-0x00007FF8E6E10000-0x00007FF8E6E20000-memory.dmp

    Filesize

    64KB

  • memory/3040-5-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-4-0x00007FF8E6E10000-0x00007FF8E6E20000-memory.dmp

    Filesize

    64KB

  • memory/3040-7-0x00007FF8E6E10000-0x00007FF8E6E20000-memory.dmp

    Filesize

    64KB

  • memory/3040-8-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-9-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-11-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-10-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-6-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-12-0x00007FF8E4C00000-0x00007FF8E4C10000-memory.dmp

    Filesize

    64KB

  • memory/3040-13-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-15-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-17-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-19-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-20-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-21-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-18-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-16-0x00007FF8E4C00000-0x00007FF8E4C10000-memory.dmp

    Filesize

    64KB

  • memory/3040-14-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB

  • memory/3040-33-0x00007FF926E2D000-0x00007FF926E2E000-memory.dmp

    Filesize

    4KB

  • memory/3040-34-0x00007FF926D90000-0x00007FF926F85000-memory.dmp

    Filesize

    2.0MB