Analysis

  • user interaction
    yes
  • max time kernel
    14s
  • max time network
    16s
  • platform
    windows11-ltsc_2024_x64
  • resource
    win11ltsc2024-20260709-en
  • resource tags

    arch:x64arch:x86image:win11ltsc2024-20260709-enlocale:en-usos:windows11-ltsc_2024-x64systemwindows
  • submitted
    10/09/2026, 23:21

General

  • Target
    RuntimeBroker.exe
  • Size 1.0MB
  • Sample260910-3b2edaxcrb
  • SHA256 cbeec773f6bbe29a464a4f56c976e647b0232973eae95635d8e224bfeb8614ab
  • MD5 SHA1 SHA512 SSDEEP TLSH

Malware Config

Signatures

  • Adds Run key to start application 2 TTPs 1 IoCs
  • Maps connected drives based on registry 3 TTPs 2 IoCs

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

  • Scheduled Task/Job: Scheduled Task 1 TTPs 1 IoCs

    Schtasks is often used by malware for persistence or to perform post-infection execution.

  • Suspicious behavior: EnumeratesProcesses 2 IoCs
  • Suspicious use of WriteProcessMemory 1 IoCs
  • Uses Task Scheduler COM API 1 TTPs

    The Task Scheduler COM API can be used to schedule applications to run on boot or at set times.

Processes

  • C:\Users\Admin\AppData\Local\Temp\RuntimeBroker.exe
    "C:\Users\Admin\AppData\Local\Temp\RuntimeBroker.exe"
    1⤵
    • Adds Run key to start application
    • Maps connected drives based on registry
    • Suspicious behavior: EnumeratesProcesses
    • Suspicious use of WriteProcessMemory
    PID:1796
    • C:\Windows\SYSTEM32\schtasks.exe
      schtasks /create /tn "MicrosoftEdgeUpdateTaskMachineGdU" /tr "C:\Users\Admin\AppData\Local\Temp\RuntimeBroker.exe" /sc onlogon /rl highest /f
      2⤵
      • Scheduled Task/Job: Scheduled Task
      PID:4232
  • C:\Users\Admin\AppData\Local\Temp\RuntimeBroker.exe
    C:\Users\Admin\AppData\Local\Temp\RuntimeBroker.exe
    1⤵
      PID:2484

    Network

          MITRE ATT&CK Enterprise v16

          Replay Monitor

          Loading Replay Monitor...

          Downloads

          memory/1796-1-0x00007FF7BE660000-0x00007FF7BE76E000-memory.dmp

          memory/2484-0-0x00007FF7BE660000-0x00007FF7BE76E000-memory.dmp