Analysis

  • max time kernel
    47s
  • max time network
    40s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20240226-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system
  • submitted
    06-06-2024 01:28

General

  • Target

    000abf705e1bb63e5225c67a0343a141ebb59061693eeca5ea0d0f32c122fd60.xlsm

  • Size

    185KB

  • MD5

    c96224caeb8417aa315329428452115f

  • SHA1

    c6854f64a4b43cac684bc7127dcd0e4cbcc7e5a8

  • SHA256

    000abf705e1bb63e5225c67a0343a141ebb59061693eeca5ea0d0f32c122fd60

  • SHA512

    31f02899acb8f4979751a646cb2e2872b31013aff78df772ca61b5bfea0308f68507b9791304af4acfe3eab73d2981afca018bf29327ad475950da111c95d631

  • SSDEEP

    3072:692pRgj0OuGSS3NuurKiw7rj3EWKp8r+z5BqoCiqFo7Uunvo+2v:6wgjp3SYuyReEWK2IBuiqFcUso+6

Score
10/10

Malware Config

Signatures

  • Process spawned unexpected child process 1 IoCs

    This typically indicates the parent process was compromised via an exploit or macro.

  • Enumerates connected drives 3 TTPs 1 IoCs

    Attempts to read the root path of hard drives other than the default C: drive.

  • 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
  • Runs net.exe
  • Suspicious behavior: AddClipboardFormatListener 1 IoCs
  • Suspicious use of FindShellTrayWindow 2 IoCs
  • Suspicious use of SetWindowsHookEx 12 IoCs
  • Suspicious use of WriteProcessMemory 2 IoCs

Processes

  • C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXE
    "C:\Program Files\Microsoft Office\Root\Office16\EXCEL.EXE" "C:\Users\Admin\AppData\Local\Temp\000abf705e1bb63e5225c67a0343a141ebb59061693eeca5ea0d0f32c122fd60.xlsm"
    1⤵
    • Checks processor information in registry
    • Enumerates system info in registry
    • Suspicious behavior: AddClipboardFormatListener
    • Suspicious use of FindShellTrayWindow
    • Suspicious use of SetWindowsHookEx
    • Suspicious use of WriteProcessMemory
    PID:4860
    • C:\Windows\System32\net.exe
      "C:\Windows\System32\net.exe" use q: [[MACROURL]]
      2⤵
      • Process spawned unexpected child process
      • Enumerates connected drives
      PID:2596
  • C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
    "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --type=utility --utility-sub-type=asset_store.mojom.AssetStoreService --lang=en-US --service-sandbox-type=asset_store_service --no-appcompat-clear --mojo-platform-channel-handle=4004 --field-trial-handle=2280,i,716736634476467098,11449718822158202904,262144 --variations-seed-version /prefetch:8
    1⤵
      PID:3560

    Network

    MITRE ATT&CK Enterprise v15

    Replay Monitor

    Loading Replay Monitor...

    Downloads

    • memory/4860-0-0x00007FFE8B830000-0x00007FFE8B840000-memory.dmp

      Filesize

      64KB

    • memory/4860-2-0x00007FFE8B830000-0x00007FFE8B840000-memory.dmp

      Filesize

      64KB

    • memory/4860-3-0x00007FFECB84D000-0x00007FFECB84E000-memory.dmp

      Filesize

      4KB

    • memory/4860-4-0x00007FFE8B830000-0x00007FFE8B840000-memory.dmp

      Filesize

      64KB

    • memory/4860-5-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-1-0x00007FFE8B830000-0x00007FFE8B840000-memory.dmp

      Filesize

      64KB

    • memory/4860-6-0x00007FFE8B830000-0x00007FFE8B840000-memory.dmp

      Filesize

      64KB

    • memory/4860-7-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-8-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-9-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-10-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-11-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-12-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-14-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-13-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-15-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-16-0x00007FFE89080000-0x00007FFE89090000-memory.dmp

      Filesize

      64KB

    • memory/4860-18-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-19-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-17-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-21-0x00007FFE89080000-0x00007FFE89090000-memory.dmp

      Filesize

      64KB

    • memory/4860-33-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-34-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-35-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-39-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-41-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB

    • memory/4860-44-0x00007FFECB7B0000-0x00007FFECB9A5000-memory.dmp

      Filesize

      2.0MB