Below are some MDB signatures for new Cuba ransomware targeting Ukraine government offices.

Copy mdb signatures to a new Notepad or similar text writer file and save it in the ClamWin database folder as a file named Sigfile.mdb, with a file type of “All Files”. Do not save the file as a text file. The file name should be Sigfile.mdb and nothing else.

Copy hdb signatures to a new Notepad or similar text writer file and save it in the ClamWin database folder as a file named Sigfile.hdb, with a file type of “All Files”. Do not save the file as a text file. The file name should be Sigfile.hdb and nothing else.

For multiple signatures, put each signature on a separate line in a Notepad or similar file. Put mdb and hdb signatures in separate files. You can add multiple signatures to the top of an existing mdb or hdb signature file. Copy the signatures, add one blank line to the top of the file and paste the signatures there—any additional lines needed will be added. Do not add signatures to the bottom of existing hdb and mdb signature files or you will get a ClamWin scanning error. Delete any blank lines between signatures in a file before saving the file.

After you save a signature file (.hdb, .mdb or .yar) in the ClamWin database folder, scan a file with ClamWin to make sure it works. If you get a scan error, accept my apology, and delete the signature file from the database folder or delete only those signatures that you just posted to an existing mdb or hdb file and re-save it after first removing any blank lines in the signature file. For multiple signature files, run a scan after you save each file to help you locate a file that could cause a scan error.

After 4 weeks, the malware will probably be updated, so you can delete mdb and hdb signatures then. The date (USA) and time (24 hr) are the last two items in each mdb and hdb signature. Yara signatures can be kept permanently if they are not for a specific malware—keep nonspecific sigs for two or three months.

Thanks to Ukraine CERT!

MDB Signatures
455680:117b89f63e9442a5cc48e6811f9d9524:Win.Trojan.Agent-102722.1411
58880:bdbc2547512b928717d92159c9caa562:Win.Trojan.Kekto-102722.1413
89600:9239429f81b132a73252768658826185:Win.Trojan.Agent-102722.1416
137216:1cd771855cdbea7a0b30b9e7d5a1701c:Win.Trojan.Agent-102722.1419
443904:5a0fb8c47d466ea724d0b06e597d5f61:Win.Trojan.Agent-102722.1420
1423360:8cf991639f1e6744f6f7eaa890bf82e3:Win.Trojan.Tedy-102722.1422
1423872:53085bf2004eaf3838a08667aa29089c:Win.Trojan.Tedy-102722.1439
108032:58db6fd771b3a4c92b20ca09f8e2744c:Win.Trojan.Agent-102722.1442
88576:e21128c59d57f5a77146e059cf7f0669:Win.Trojan.Agent-102722.1444
43008:2780bd5dbf6d7bc23e18e6dd7ade10a4:Win.Trojan.Jaik-102722.1446
472064:3d1db1d080caf9bc4dda2008c67baf8b:Win.Trojan.Lazy-102722.1448
42496:a8cf246234c139218cd806e9d71a4dc7:Win.Trojan.Agent-102722.1450