{"id":2874,"date":"2024-09-25T20:17:31","date_gmt":"2024-09-25T20:17:31","guid":{"rendered":"https:\/\/xdr-mdr.lmntrix.com\/main_web\/?p=2874"},"modified":"2025-07-29T05:53:33","modified_gmt":"2025-07-29T05:53:33","slug":"gandcrab-ransomware-scuttles-files-demands-tor-download-to-retrieve-files","status":"publish","type":"post","link":"https:\/\/lmntrix.com\/blog\/gandcrab-ransomware-scuttles-files-demands-tor-download-to-retrieve-files\/","title":{"rendered":"GandCrab ransomware scuttles files, demands TOR download to retrieve files"},"content":{"rendered":"<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img fetchpriority=\"high\" decoding=\"async\" width=\"500\" height=\"280\" src=\"https:\/\/lmntrix.com\/blog\/wp-content\/uploads\/2024\/09\/crabs-950463_960_720.webp\" alt=\"crabs\" class=\"wp-image-2881\"\/><\/figure>\n<\/div>\n\n\n<p>Over the last three days LMNTRIX Labs has been tracking an influx of GandCrab ransomware. The ransomware samples are being pushed by RIG Exploit delivery channels. \u00a0<br><br>The sample we discovered for analysis is: 5d53050a1509bcc9d97552fa52c1105b51967f4ccf2bde717b502605db1b5011<br><br>File size: 129 KB<br><br><strong>Infection<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"395\" src=\"https:\/\/lmntrix.com\/blog\/wp-content\/uploads\/2024\/09\/1-6-1-1024x395.webp\" alt=\"\" class=\"wp-image-2875\"\/><\/figure>\n\n\n\n<p><em>Figure 1 Ransom_GANDCRAB detection<\/em><br><br>Versions and resources of both the files are same:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"229\" height=\"66\" src=\"https:\/\/lmntrix.com\/blog\/wp-content\/uploads\/2024\/09\/2-6-1.webp\" alt=\"\" class=\"wp-image-2876\"\/><\/figure>\n\n\n\n<p><em>Figure 2 Resource -Icon of the file<\/em><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"254\" height=\"215\" src=\"https:\/\/lmntrix.com\/blog\/wp-content\/uploads\/2024\/09\/3-5-2.webp\" alt=\"\" class=\"wp-image-2877\"\/><\/figure>\n\n\n\n<p><em>Figure 3 Versions details of both\u00a0the ransomware samples<\/em><br><br><strong>Encryption<\/strong><br><br>We loaded the sample in our debugger to further explore the malware\u2019s behaviour:<br><br>00401424 \u00a0 |. \u00a0FF15 54F04000 \u00a0CALL DWORD PTR DS:[&lt;&amp;KERNEL32.GlobalAlloc>] \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0; \\GlobalAlloc<br><br>GlobalAlloc functions are used in memory management, mostly in decrypting or decoding the codes in the file.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"741\" height=\"288\" src=\"https:\/\/lmntrix.com\/blog\/wp-content\/uploads\/2024\/09\/4-5-1.webp\" alt=\"\" class=\"wp-image-2878\"\/><\/figure>\n\n\n\n<p><em>Figure 4 decoding functions<\/em><\/p>\n\n\n\n<p>We traversed to the highlighted subroutines in the above snapshot: Address 4011F1. When we execute all those instructions, we arrived at the below location:<br><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"864\" height=\"53\" src=\"https:\/\/lmntrix.com\/blog\/wp-content\/uploads\/2024\/09\/5-4-3.webp\" alt=\"\" class=\"wp-image-2879\"\/><\/figure>\n\n\n\n<p><br><em>Figure 5 Jmp to decrypting code<\/em><br><br>After further debugging the code, we found the file included a number of anti-debugging tricks:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>0405927: call dword ptr [0040F0CCh] &nbsp; &nbsp;\/\/<strong>IsDebuggerPresent@KERNEL32.DLL&nbsp;<\/strong><\/td><\/tr><tr><td>040592d: mov dword ptr [004153B8h], eax<\/td><\/tr><tr><td>040593a: push 00000000h&nbsp;<\/td><\/tr><tr><td>040593c: call dword ptr [0040F0C8h] &nbsp; \/\/<strong>SetUnhandledExceptionFilter@KERNEL32.DLL&nbsp;<\/strong><\/td><\/tr><tr><td>0405942: push 0040F530h&nbsp;<\/td><\/tr><tr><td>0405947: call dword ptr [0040F0C4h] &nbsp; &nbsp;\/\/<strong>UnhandledExceptionFilter@KERNEL32.DLL&nbsp;<\/strong><\/td><\/tr><tr><td>040594d: cmp dword ptr [004153B8h], 00000000h&nbsp;<\/td><\/tr><tr><td>0405954: jne 0040595Eh<\/td><\/tr><tr><td>0405956: push 00000001h&nbsp;<\/td><\/tr><tr><td>0405958: call 00409B47h<\/td><\/tr><tr><td>040595d: pop ecx&nbsp;<\/td><\/tr><tr><td>040595e: push C0000409h&nbsp;<\/td><\/tr><tr><td>0405963: call dword ptr [0040F0C0h] &nbsp; &nbsp;\/\/<strong>GetCurrentProcess@KERNEL32.DLL&nbsp;<\/strong><\/td><\/tr><tr><td>0405969: push eax&nbsp;<\/td><\/tr><tr><td>040596a: call dword ptr [0040F068h] &nbsp; \/\/<strong>TerminateProcess@KERNEL32.DLL<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>The above code all centres on anti-debugging tricks. We also observed multiple network-related artefacts in the code:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>0406ddb: push dword ptr [esi+04h]&nbsp;<\/td><\/tr><tr><td>0406dde: call dword ptr [004091D0h] &nbsp; \/\/InternetConnectW@WININET.DLL&nbsp;<\/td><\/tr><tr><td>0406e2a: push 00410938h &nbsp; &nbsp;\/\/HTTP\/1.1&nbsp;<\/td><\/tr><tr><td>0406e30: push dword ptr [ebp+28h]&nbsp;<\/td><\/tr><tr><td>0406e34: call dword ptr [004091C4h] &nbsp; &nbsp;\/\/HttpOpenRequestW@WININET.DLL&nbsp;<\/td><\/tr><tr><td>0406e4d: call dword ptr [004091C0h] &nbsp; &nbsp;\/\/HttpSendRequestW@WININET.DLL&nbsp;<\/td><\/tr><tr><td>0406e96: call dword ptr [004091D4h] &nbsp; &nbsp;\/\/InternetReadFile@WININET.DLL&nbsp;<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>These instructions are picked selectively to spot network connection calls. During our analysis, we observed the malware contact the following domains:<br><br>\u2022&nbsp;&nbsp; &nbsp;ipv4bot.whatismyipaddress.com \u2013 this is used to detect the network\u2019s IP address.<br><br>\u2022&nbsp;&nbsp; &nbsp;a.dnspod(.)com \u2013 we checked this in Virustotal which Fortinet AV flagged as malware.<br><br><strong>Registry entries and file creation:<\/strong><br><br>A duplicate MD5 of the parent file is dropped in the %appdata%\\Microsoft folder with a random name.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>C:\\Documents and Settings\\UserName\\Application Data\\Microsoft\\wgpspj.exe<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>And same file is targeted in the created registry key:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce &#8220;ulclieptfog&#8221;<br>Type: REG_SZ<br>Data: &#8220;C:\\Documents and Settings\\UserName\\Application Data\\Microsoft\\wgpspj.exe&#8221;<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>To find the randomness of the file name and registry key value, we reverted to the clean state before executing the file. A duplicate file gets created with &lt;random name.exe&gt;. The \u2018Runonce\u2019 key\u2019s value part is also randomly generated. An example is below:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>C:\\Documents and Settings\\UserName\\Application Data\\Microsoft\\&lt;random file name.exe&gt;<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Random value:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnce &#8220;&lt;random value part&gt;&#8221;<br>Type: REG_SZ<br>Data: &#8220;C:\\Documents and Settings\\UserName\\Application Data\\Microsoft\\&lt;random file name.exe&gt;&#8221;<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>In %appdata% location, the malware drops a text file called \u2018GDCB-DECRYPT.txt\u2019. This contains the malware\u2019s ransom note. The user is instructed to purchase a private key after downloading the Tor browser:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"301\" height=\"352\" src=\"https:\/\/lmntrix.com\/blog\/wp-content\/uploads\/2024\/09\/6-4-1.webp\" alt=\"\" class=\"wp-image-2880\"\/><\/figure>\n\n\n\n<p><em>Figure 6 GDGB-DECRYPT.txt<\/em><br><br><strong>Threat Indicators \u2013 IOC details<\/strong><br><br>File Hashes:<br><br>SHA 256: 5d53050a1509bcc9d97552fa52c1105b51967f4ccf2bde717b502605db1b5011<br><br>Malicious domain:<br><br>a.dnspod(.)com<br><br>TOR Link:<br><br>hxxp:\/\/gdcbghvjyqy7jclk.onion.top\/259a4fdc3766943<br><br>hxxp:\/\/ gdcbghvjyqy7jclk.onion.casa\/259a4fdc3766943<br><br>hxxp:\/\/gdcbghvjyqy7jclk.onion.guide\/259a4fdc3766943<br><br>File extension added by this variant of ransomware:<br><br>.GDCB<br><br>Registry key:<br><br>Key: HKCU\\SOFTWARE\\MICROSOFT\\WINDOWS\\CURRENTVERSION\\RUNONCE&#8221; \u00a0<br><br>Value: &#8220;Random value name on each execution&#8221;<br><br>Physical location: %appdata% under &lt;Microsoft folder> &lt;Random file name on each execution><br><br><strong>Conclusion<\/strong><br><br>We advise users to apply the IOC details and set alerts in order to prevent infection. Further, users should always exercise caution when receiving attachments from unknown users.\u00a0<br><br>Updated anti-malware with anti-ransomware modules can also help combat ransomware attacks.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Over the last three days LMNTRIX Labs has been tracking an influx of GandCrab ransomware. The ransomware samples are being pushed by RIG Exploit delivery channels. &nbsp; The sample we discovered for analysis is: 5d53050a1509bcc9d97552fa52c1105b51967f4ccf2bde717b502605db1b5011 File size: 129 KB Infection Figure 1 Ransom_GANDCRAB detection Versions and resources of both the files are same: Figure 2 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2881,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21],"tags":[],"class_list":["post-2874","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-labs"],"_links":{"self":[{"href":"https:\/\/lmntrix.com\/blog\/wp-json\/wp\/v2\/posts\/2874","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lmntrix.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lmntrix.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lmntrix.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lmntrix.com\/blog\/wp-json\/wp\/v2\/comments?post=2874"}],"version-history":[{"count":6,"href":"https:\/\/lmntrix.com\/blog\/wp-json\/wp\/v2\/posts\/2874\/revisions"}],"predecessor-version":[{"id":4297,"href":"https:\/\/lmntrix.com\/blog\/wp-json\/wp\/v2\/posts\/2874\/revisions\/4297"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/lmntrix.com\/blog\/wp-json\/wp\/v2\/media\/2881"}],"wp:attachment":[{"href":"https:\/\/lmntrix.com\/blog\/wp-json\/wp\/v2\/media?parent=2874"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lmntrix.com\/blog\/wp-json\/wp\/v2\/categories?post=2874"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lmntrix.com\/blog\/wp-json\/wp\/v2\/tags?post=2874"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}