Analysis

  • max time kernel
    151s
  • max time network
    44s
  • platform
    windows7_x64
  • resource
    win7-20220812-en
  • resource tags

    arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system
  • submitted
    13-10-2022 18:28

General

  • Target

    64ME_bul8.exe

  • Size

    666KB

  • MD5

    ac8d418b660f7c9585ac97fe524abe8f

  • SHA1

    653ecc2e07739e59bd5500f535c3f5c6e3d27060

  • SHA256

    61c26b20a2b291252ccf1b2ae4319542df526e820f96ad4667478ab101b6ee1f

  • SHA512

    edf33e15bb1d8f97799d25281429451ece9df0ae8c9ead93c301beeac851d802d501d7362c86cee6afb0a2772d58dbef1b17afe9ba84b83324f3959cf2fa7b1c

  • SSDEEP

    12288:ZYW1LNT35lDbK/LIVaN8+T7vwqyqhYMhWt918vulA/C9+m:dd35lDbKDIwWUDyqS5omqC9+

Malware Config

Extracted

Path

C:\MSOCache\All Users\{90140000-0011-0000-0000-0000000FF1CE}-C\!-Recovery_Instructions-!.html

Ransom Note
<!DOCTYPE html> <html lang="en"> <head> <meta charset='utf-8'> <meta name='viewport' content='width=device-width,initial-scale=1'> <title></title> <style> html, body { background-color: #1a1a1a; } body { padding-top: 1rem !important; font-size: 1.3rem; color: white; } #text h2 { font-size: 2rem; font-weight: 600; line-height: 1.125; } .container { max-width: 1152px; flex-grow: 1; margin: 0 auto; position: relative; width: auto; } .box { background-color: #242424; display: block; padding: 1.25rem; border: 1px solid #303030; } a { color: #00b4d8; text-decoration: none; } a:hover { text-decoration: underline; } li { margin-bottom: 10px; } </style> </head> <body> <div class='container'> <div class='box'> <div id='text'> <h2>If you get this message, your network was hacked!</h2> <p>After we gained full access to your servers, we first downloaded a large amount of sensitive data and then encrypted all the data stored on them.</p> <p>That includes personal information on your clients, partners, your personnel, accounting documents, and other crucial files that are necessary for your company to work normally.</p> <p>We used modern complicated algorithms, so you or any recovery service will not be able to decrypt files without our help, wasting time on these attempts instead of negotiations can be fatal for your company.</p> <p>Make sure to act within <span style='color:#f4a261;'>72</span> hours or the negotiations will be considered failed!</p> <p>Inform your superior management about what's going on.</p> <p> Contact us for price and get decryption software.</p> <p> Contact us by email:<p> <h2>[email protected]</h2> </p>If you will get no answer within 24 hours contact us by our alternate emails:</p> <h2>[email protected]</h2> </p>To verify the possibility of the recovery of your files we can decrypted 1-3 file for free.</p> </p>Attach file to the letter (no more than 5Mb).</p> <h2>If you and us succeed the negotiations we will grant you:</h2> <ul> <li>complete confidentiality, we will keep in secret any information regarding to attack, your company will act as if nothing had happened.</li> <li>comprehensive information about vulnerabilities of your network and security report.</li> <li>software and instructions to decrypt all the data that was encrypted.</li> <li>all sensitive downloaded data will be permanently deleted from our cloud storage and we will provide an erasure log.</li> </ul> <h2>Our options if you act like nothing's happening, refuse to make a deal or fail the negotiations:</h2> <ul> <li>inform the media and independent journalists about what happened to your servers. To prove it we'll publish a chunk of private data that you should have ciphered if you care about potential breaches. Moreover, your company will inevitably take decent reputational loss which is hard to assess precisely.</li> <li>inform your clients, employees, partners by phone, e-mail, sms and social networks that you haven't prevent their data leakage. You will violate laws about private data protection.</li> <li>start DDOS attack on you website and infrastructures.</li> <li>personal data stored will be put on sale on the Darknet to find anyone interested to buy useful information regarding your company. It could be data mining agencies or your market competitors.</li> <li>publish all the discovered vulnerabilities found in your network, so anyone will do anything with it.</li> </ul> <h2>Why pay us?</h2> <p>We care about our reputation. You are welcome to google our cases up and be sure that we don't have a single case of failure to provide what we promissed.</p> <p>Turning this issue to a bug bounty will save your private information, reputation and will allow you to use the security report and avoid this kind of situations in future.</p> <h2>Your personal ID</p> CD33216ED4A9AB1603983E1885708155B4CF60320DED9E74D1366A8680A0715FB56A7C87FE47BDF0ABF0E1A4220579C7495350328C80CE04D74907363EECD365<br>C69FEB7377C338DC8C8BF3E55233609B6D53B13C3E60AEF4B201000E9B52A101C74322ACC7DE142752F9BB9CD22281ADEFF779849E8CFF6BA637FE7B1988<br>369C8F7439994B36CD2DF7571834AD4C3D066A28A836D58BAC582EF02AA15023C5416CA71CBC6F3F0E66843B9796CD6A7C400C9ECFC21FF71594E88E4A96<br>2F583508A255C4A70FC62DED4D40712820F09EEE9A672073A1994557626C90F1C032277090C3850176A2CAFB6BE5E46BB566935808E0B7B8FAE51DE3E2E1<br>EFCD20B232249E869C1E1F81C4E44105E4656B5E126BF5AC0800469B64703012875410D97B8ECEBA9A02E833083D368932C30DD6899A52D946D05279ED10<br>1D219AF84B7CED43332BAE4B9EE66752962B42B13A9D2F77A6AA29A46DDA6DDB6789320117934D9F649C040A86DB1FFD366FA0B2DF4BE1B320C26942E411<br>43210DACAF25187485DC7AFA863D04671B1F326A64983248EBBBC061C099FA1AE09D5D2DEA00C8A810AB2E16BDFC268FA5F356BB55DCE2A181A695412D5B<br>5BE7F4B4BA589836A228408ACE72DC36CC035950BDB36573A65533DBBB7B6525747ECA046B135E363AE1F893D3F0290981AF40EDDBC9B4BB58C382FD7973<br>8B59D4C2A38DA2A01CB364144F14
Emails

<h2>[email protected]</h2>

<h2>[email protected]</h2>

Signatures

  • MedusaLocker

    Ransomware with several variants first seen in September 2019.

  • MedusaLocker payload 2 IoCs
  • UAC bypass 3 TTPs 2 IoCs
  • Deletes shadow copies 2 TTPs

    Ransomware often targets backup files to inhibit system recovery.

  • Detects MedusaLocker ransomware 2 IoCs
  • Executes dropped EXE 1 IoCs
  • Modifies extensions of user files 8 IoCs

    Ransomware generally changes the extension on encrypted files.

  • Reads user/profile data of web browsers 2 TTPs

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

  • Checks whether UAC is enabled 1 TTPs 1 IoCs
  • Drops desktop.ini file(s) 1 IoCs
  • Enumerates connected drives 3 TTPs 24 IoCs

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

  • Enumerates physical storage devices 1 TTPs

    Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.

  • Interacts with shadow copies 2 TTPs 3 IoCs

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

  • Suspicious behavior: EnumeratesProcesses 64 IoCs
  • Suspicious use of AdjustPrivilegeToken 63 IoCs
  • Suspicious use of WriteProcessMemory 28 IoCs
  • System policy modification 1 TTPs 3 IoCs

Processes

  • C:\Users\Admin\AppData\Local\Temp\64ME_bul8.exe
    "C:\Users\Admin\AppData\Local\Temp\64ME_bul8.exe"
    1⤵
    • UAC bypass
    • Modifies extensions of user files
    • Checks whether UAC is enabled
    • Drops desktop.ini file(s)
    • Enumerates connected drives
    • Suspicious behavior: EnumeratesProcesses
    • Suspicious use of WriteProcessMemory
    • System policy modification
    PID:1672
    • C:\Windows\SysWOW64\vssadmin.exe
      vssadmin.exe Delete Shadows /All /Quiet
      2⤵
      • Interacts with shadow copies
      PID:984
    • C:\Windows\SysWOW64\Wbem\wmic.exe
      wmic.exe SHADOWCOPY /nointeractive
      2⤵
      • Suspicious use of AdjustPrivilegeToken
      PID:1908
    • C:\Windows\SysWOW64\vssadmin.exe
      vssadmin.exe Delete Shadows /All /Quiet
      2⤵
      • Interacts with shadow copies
      PID:1320
    • C:\Windows\SysWOW64\Wbem\wmic.exe
      wmic.exe SHADOWCOPY /nointeractive
      2⤵
      • Suspicious use of AdjustPrivilegeToken
      PID:1072
    • C:\Windows\SysWOW64\vssadmin.exe
      vssadmin.exe Delete Shadows /All /Quiet
      2⤵
      • Interacts with shadow copies
      PID:660
    • C:\Windows\SysWOW64\Wbem\wmic.exe
      wmic.exe SHADOWCOPY /nointeractive
      2⤵
      • Suspicious use of AdjustPrivilegeToken
      PID:1676
  • C:\Windows\system32\vssvc.exe
    C:\Windows\system32\vssvc.exe
    1⤵
    • Suspicious use of AdjustPrivilegeToken
    PID:1108
  • C:\Windows\system32\taskeng.exe
    taskeng.exe {4BAADC82-3C6A-4879-9852-E3CD35AECEC8} S-1-5-21-999675638-2867687379-27515722-1000:ORXGKKZC\Admin:Interactive:[1]
    1⤵
    • Suspicious use of WriteProcessMemory
    PID:584
    • C:\Users\Admin\AppData\Roaming\svhost.exe
      C:\Users\Admin\AppData\Roaming\svhost.exe
      2⤵
      • Executes dropped EXE
      PID:1972

Network

MITRE ATT&CK Enterprise v6

Replay Monitor

Loading Replay Monitor...

Downloads

  • C:\Users\Admin\AppData\Roaming\svhost.exe

    Filesize

    666KB

    MD5

    ac8d418b660f7c9585ac97fe524abe8f

    SHA1

    653ecc2e07739e59bd5500f535c3f5c6e3d27060

    SHA256

    61c26b20a2b291252ccf1b2ae4319542df526e820f96ad4667478ab101b6ee1f

    SHA512

    edf33e15bb1d8f97799d25281429451ece9df0ae8c9ead93c301beeac851d802d501d7362c86cee6afb0a2772d58dbef1b17afe9ba84b83324f3959cf2fa7b1c

  • C:\Users\Admin\AppData\Roaming\svhost.exe

    Filesize

    666KB

    MD5

    ac8d418b660f7c9585ac97fe524abe8f

    SHA1

    653ecc2e07739e59bd5500f535c3f5c6e3d27060

    SHA256

    61c26b20a2b291252ccf1b2ae4319542df526e820f96ad4667478ab101b6ee1f

    SHA512

    edf33e15bb1d8f97799d25281429451ece9df0ae8c9ead93c301beeac851d802d501d7362c86cee6afb0a2772d58dbef1b17afe9ba84b83324f3959cf2fa7b1c

  • memory/660-59-0x0000000000000000-mapping.dmp

  • memory/984-55-0x0000000000000000-mapping.dmp

  • memory/1072-58-0x0000000000000000-mapping.dmp

  • memory/1320-57-0x0000000000000000-mapping.dmp

  • memory/1672-54-0x0000000075BD1000-0x0000000075BD3000-memory.dmp

    Filesize

    8KB

  • memory/1676-60-0x0000000000000000-mapping.dmp

  • memory/1908-56-0x0000000000000000-mapping.dmp

  • memory/1972-62-0x0000000000000000-mapping.dmp