Overview

overview

10

Static

static

3

sub_16cc7519945b.exe

windows10-2004-x64

10

sub_16cc7519945b.exe

windows11-21h2-x64

10

Analysis

  • max time kernel
    149s
  • max time network
    147s
  • platform
    windows10-2004_x64
  • resource
    win10v2004-20260513-en
  • resource tags

    arch:x64arch:x86image:win10v2004-20260513-enlocale:en-usos:windows10-2004-x64systemwindows
  • submitted
    24/05/2026, 01:27

Sharing

Copy URL Twitter E-mail
Report Analysis Logs

General

  • Target
    sub_16cc7519945b.exe
  • Size 163KB
  • Sample260524-bt764agy31
  • SHA256 16cc7519945bace49ef729e69db7d19e00252f2bd559903e1631c8878c2360f4
  • MD5 SHA1 SHA512 SSDEEP TLSH
Score
10/10
credential_accessdiscoverycontiransomwarespywarestealer

Malware Config

Extracted

Path

  • C:\Program Files (x86)\readme.txt

  • conti

Ransom Note
  • All of your files are currently encrypted by CONTI strain. If you don't know who we are - just "Google it." As you already know, all of your data has been encrypted by our software. It cannot be recovered by any means without contacting our team directly. DON'T TRY TO RECOVER your data by yourselves. Any attempt to recover your data (including the usage of the additional recovery software) can damage your files. However, if you want to try - we recommend choosing the data of the lowest value. DON'T TRY TO IGNORE us. We've downloaded a pack of your internal data and are ready to publish it on our news website if you do not respond. So it will be better for both sides if you contact us as soon as possible. DON'T TRY TO CONTACT feds or any recovery companies. We have our informants in these structures, so any of your complaints will be immediately directed to us. So if you will hire any recovery company for negotiations or send requests to the police/FBI/investigators, we will consider this as a hostile intent and initiate the publication of whole compromised data immediately. To prove that we REALLY CAN get your data back - we offer you to decrypt two random files completely free of charge. You can contact our team directly for further instructions through our website : TOR VERSION : (you should download and install TOR browser first https://torproject.org) http://contirec7nchr45rx6ympez5rjldibnqzh7lsa56lvjvaeywhvoj3wad.onion/WopXZ9Pm5nFBPcUKJV8pgTiGnvgeL4pkSTv2h01krJNlw1Y1L8QGRcX66W6qw7Wl YOU SHOULD BE AWARE! We will speak only with an authorized person. It can be the CEO, top management, etc. In case you are not such a person - DON'T CONTACT US! Your decisions and action can result in serious harm to your company! Inform your supervisors and stay calm!
URLs

  • http://contirec7nchr45rx6ympez5rjldibnqzh7lsa56lvjvaeywhvoj3wad.onion/WopXZ9Pm5nFBPcUKJV8pgTiGnvgeL4pkSTv2h01krJNlw1Y1L8QGRcX66W6qw7Wl

Signatures

  • Family: Conti Ransomware

    Ransomware generally thought to be a successor to Ryuk.

    ransomwareconti
  • Renames multiple (9269) files with added filename extension

    This suggests ransomware activity of encrypting all the files on the system.

    ransomware
  • Credentials from Password Stores: Windows Credential Manager 1 TTPs

    Suspicious access to Credentials History.

    credential_accessstealer
  • Drops startup file 1 IoCs
  • Reads user/profile data of web browsers 3 TTPs

    Infostealers often target stored browser data, which can include saved credentials etc.

    spywarestealer
  • Network Share Discovery 1 TTPs

    Attempt to gather information on host network.

    discovery
  • Sets desktop wallpaper using registry 2 TTPs 1 IoCs
    ransomware
  • Drops file in Program Files directory 64 IoCs
  • Browser Information Discovery 1 TTPs

    Enumerate browser information.

    discovery
  • System Location Discovery: System Language Discovery 1 TTPs 58 IoCs

    Attempt gather information about the system language of a victim in order to infer the geographical location of that host.

    discovery
  • Runs net.exe
  • Suspicious behavior: EnumeratesProcesses 64 IoCs
  • Suspicious use of AdjustPrivilegeToken 45 IoCs
  • Suspicious use of WriteProcessMemory 58 IoCs
  • Uses Volume Shadow Copy service COM API

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

    ransomware

Processes

  • C:\Users\Admin\AppData\Local\Temp\sub_16cc7519945b.exe
    "C:\Users\Admin\AppData\Local\Temp\sub_16cc7519945b.exe"
    1⤵
    • Drops startup file
    • Sets desktop wallpaper using registry
    • Drops file in Program Files directory
    • System Location Discovery: System Language Discovery
    • Suspicious behavior: EnumeratesProcesses
    • Suspicious use of WriteProcessMemory
    PID:4116
    • C:\Windows\System32\wbem\WMIC.exe
      shadowcopy where "ID='{5DDE8FD1-84CF-4F65-A1A6-9A681A9243AC}'" delete
      2⤵
      • Suspicious use of AdjustPrivilegeToken
      PID:4400
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop "SQLsafe Backup Service" /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:5040
      • C:\Windows\SysWOW64\net.exe
        net stop "SQLsafe Backup Service" /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:2136
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop "SQLsafe Backup Service" /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:3696
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop "SQLsafe Filter Service" /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:1692
      • C:\Windows\SysWOW64\net.exe
        net stop "SQLsafe Filter Service" /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:4340
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop "SQLsafe Filter Service" /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:1220
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSOLAP$SQL_2008 /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:4756
      • C:\Windows\SysWOW64\net.exe
        net stop MSOLAP$SQL_2008 /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:4548
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSOLAP$SQL_2008 /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:540
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$BKUPEXEC /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:2416
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$BKUPEXEC /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:2032
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$BKUPEXEC /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:4648
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$ECWDB2 /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:2296
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$ECWDB2 /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:3140
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$ECWDB2 /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:4892
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$PRACTICEMGT /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:2676
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$PRACTICEMGT /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:8
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$PRACTICEMGT /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:3044
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$PRACTTICEBGC /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:2100
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$PRACTTICEBGC /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:2516
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$PRACTTICEBGC /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:1528
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$PROFXENGAGEMENT /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:4388
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$PROFXENGAGEMENT /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:4020
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$PROFXENGAGEMENT /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:3020
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$SBSMONITORING /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:1404
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$SBSMONITORING /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:472
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$SBSMONITORING /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:2300
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$SHAREPOINT /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:2380
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$SHAREPOINT /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:5012
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$SHAREPOINT /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:1468
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$SQL_2008 /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:1812
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$SQL_2008 /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:4940
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$SQL_2008 /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:2476
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$SYSTEM_BGC /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:3808
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$SYSTEM_BGC /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:4392
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$SYSTEM_BGC /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:812
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$TPS /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:4636
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$TPS /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:2900
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$TPS /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:2072
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$TPSAMA /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:3728
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$TPSAMA /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:4640
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$TPSAMA /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:1748
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$VEEAMSQL2008R2 /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:3784
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$VEEAMSQL2008R2 /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:4580
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$VEEAMSQL2008R2 /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:3368
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQL$VEEAMSQL2012 /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:4300
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQL$VEEAMSQL2012 /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:1852
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQL$VEEAMSQL2012 /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:3532
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop MSSQLSERVER /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:5044
      • C:\Windows\SysWOW64\net.exe
        net stop MSSQLSERVER /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:284
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop MSSQLSERVER /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:3352
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop SQLBrowser /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:4836
      • C:\Windows\SysWOW64\net.exe
        net stop SQLBrowser /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:2492
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop SQLBrowser /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:408
    • C:\Windows\SysWOW64\cmd.exe
      cmd.exe /c net stop SQLWriter /y
      2⤵
      • System Location Discovery: System Language Discovery
      • Suspicious use of WriteProcessMemory
      PID:4708
      • C:\Windows\SysWOW64\net.exe
        net stop SQLWriter /y
        3⤵
        • System Location Discovery: System Language Discovery
        • Suspicious use of WriteProcessMemory
        PID:3348
        • C:\Windows\SysWOW64\net1.exe
          C:\Windows\system32\net1 stop SQLWriter /y
          4⤵
          • System Location Discovery: System Language Discovery
          PID:3504
  • C:\Windows\system32\vssvc.exe
    C:\Windows\system32\vssvc.exe
    1⤵
    • Suspicious use of AdjustPrivilegeToken
    PID:4228

Network

        MITRE ATT&CK Enterprise v16

        Replay Monitor

        Loading Replay Monitor...

        Downloads

        readme.txt
        • Path C:\Program Files (x86)\readme.txt
        • Size 1KB
        • SHA256 8545d5c37ac97907cb4711c3e0059ee075b7c71adc9cb9e31d927f5b5fffc3b1
        • MD5 SHA1 SHA512 TLSH
        Submit Download