Analysis

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

    arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system
  • submitted
    29-02-2024 21:37

General

  • Target

    af881fe77287babe7bebd52f8f92ec60.xls

  • Size

    35KB

  • MD5

    af881fe77287babe7bebd52f8f92ec60

  • SHA1

    64905c894f88bba3edb42c3c3e6968e0e4f85e54

  • SHA256

    0fb8bd016f5115d376938593c542facb9d3af7cd21df17bbca07764ed96b5ebb

  • SHA512

    f1755a63bd038688fb792b592ce5f42d9c550b233fc0a929b019a3dd78f3f758e413750f5857330fbab91e4e7e3127db0226f6c01c1c98ea087e8dae18c94720

  • SSDEEP

    768:TPqNk3hbdlylKsgqopeJBWhZFGkE+cL2NdAJeGsuI4dVIvePERr:Lok3hbdlylKsgqopeJBWhZFGkE+cL2NV

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.

  • 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
  • Modifies registry class 1 IoCs
  • Suspicious behavior: AddClipboardFormatListener 1 IoCs
  • Suspicious use of FindShellTrayWindow 1 IoCs
  • Suspicious use of SetWindowsHookEx 6 IoCs
  • Suspicious use of WriteProcessMemory 4 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\af881fe77287babe7bebd52f8f92ec60.xls"
    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:3524
    • C:\Windows\explorer.exe
      explorer.exe C:\Users\Public\Documents\Xyb1p.vbs
      2⤵
      • Process spawned unexpected child process
      PID:2488
  • C:\Windows\explorer.exe
    C:\Windows\explorer.exe /factory,{75dff2b7-6936-4c06-a8bb-676a7b00b24b} -Embedding
    1⤵
    • Modifies registry class
    • Suspicious use of WriteProcessMemory
    PID:4680
    • C:\Windows\System32\WScript.exe
      "C:\Windows\System32\WScript.exe" "C:\Users\Public\Documents\Xyb1p.vbs"
      2⤵
        PID:2344
    • 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=1340 --field-trial-handle=2356,i,13261194862334667799,7441241219475888176,262144 --variations-seed-version /prefetch:8
      1⤵
        PID:2776

      Network

      MITRE ATT&CK Enterprise v15

      Replay Monitor

      Loading Replay Monitor...

      Downloads

      • C:\Users\Public\Documents\Xyb1p.vbs

        Filesize

        578B

        MD5

        c49723b7bea82ad1c6a7db1d67c1f73f

        SHA1

        aec0ae26eb79a615924ed73f0696901f8f923249

        SHA256

        631a1ede642ba292f653a8d409814914660bb8aa0b99feab49408f5aecbdee52

        SHA512

        2ca819833b4bf68ef13da138d0e4ff0943a934e9ae81f421e2b1472fb10ded4b868bcab3189a0013c3fe1c33fe50b0dbc47d6a9894db11e2e4e01f793e709e8e

      • memory/3524-12-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-30-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-11-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-4-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-5-0x00007FFF84CF0000-0x00007FFF84D00000-memory.dmp

        Filesize

        64KB

      • memory/3524-6-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-7-0x00007FFF84CF0000-0x00007FFF84D00000-memory.dmp

        Filesize

        64KB

      • memory/3524-9-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-8-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-14-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-3-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-1-0x00007FFF84CF0000-0x00007FFF84D00000-memory.dmp

        Filesize

        64KB

      • memory/3524-10-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-15-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-13-0x00007FFF82AD0000-0x00007FFF82AE0000-memory.dmp

        Filesize

        64KB

      • memory/3524-16-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-17-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-18-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-19-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-20-0x00007FFFC4C70000-0x00007FFFC4E65000-memory.dmp

        Filesize

        2.0MB

      • memory/3524-21-0x00007FFF82AD0000-0x00007FFF82AE0000-memory.dmp

        Filesize

        64KB

      • memory/3524-2-0x00007FFF84CF0000-0x00007FFF84D00000-memory.dmp

        Filesize

        64KB

      • memory/3524-0-0x00007FFF84CF0000-0x00007FFF84D00000-memory.dmp

        Filesize

        64KB