{"id":33819,"date":"2024-07-05T13:24:45","date_gmt":"2024-07-05T17:24:45","guid":{"rendered":"https:\/\/www.kaspersky.com.au\/blog\/cve-2024-6387-regresshion-researcher-attack\/33819\/"},"modified":"2024-07-06T04:42:10","modified_gmt":"2024-07-05T17:42:10","slug":"cve-2024-6387-regresshion-researcher-attack","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com.au\/blog\/cve-2024-6387-regresshion-researcher-attack\/33819\/","title":{"rendered":"Attack on cybersecurity researchers: pseudo-exploit for regreSSHion"},"content":{"rendered":"<p>An archive containing malicious code is being distributed on the social network X (formerly known as Twitter), under the guise of an exploit for the recently discovered <a href=\"https:\/\/www.kaspersky.com\/blog\/openssh-vulnerability-mitigation-cve-2024-6387-regresshion\/51603\/\" target=\"_blank\" rel=\"noopener nofollow\">CVE-2024-6387 aka regreSSHion<\/a>. According to our experts, this may be an attempt to attack cybersecurity specialists. In this post we explain what actually is in the archive and how attackers are trying to lure researchers into a trap.<\/p>\n<h2>The legend behind the archive<\/h2>\n<p>Presumably, there is a server that has a working exploit for the CVE-2024-6387 vulnerability in OpenSSH. Moreover, this server actively uses this exploit to attack a list of IP addresses. The archive, offered to anyone wishing to investigate this attack, allegedly contains a working exploit, a list of IP addresses and some kind of payload.<\/p>\n<h2>Real contents of the malicious archive<\/h2>\n<p>In fact, the archive contains some source code, a set of malicious binaries and scripts. The source code looks like a slightly edited version of a non-functional proof-of-concept for this vulnerability, which was already distributed in the public domain.<\/p>\n<p>One of the scripts, written in Python, simulates the exploitation of a vulnerability on servers located at IP addresses from the list. In reality, it launches a malicious file called <em>exploit<\/em> \u2014 a malware that serves to achieve persistence in the system and to retrieve additional payload from a remote server. The malicious code is saved in a file located at the <em>\/etc\/cron.hourly<\/em> directory. In order to achieve persistence, it modifies the <em>ls<\/em> file and writes a copy of itself into it, repeating the execution of malicious code every time it is launched.<\/p>\n<h2>How to Stay Safe<\/h2>\n<p>Apparently, the authors of the attack are counting on the fact that, when working with obviously malicious code, researchers tend to disable security solutions and focus on analyzing the exchange of data between the malware and a server vulnerable to CVE-2024-6387. Meanwhile, completely different malicious code will be used to compromise the researchers\u2019 computers.<\/p>\n<p>Therefore, we remind all information security experts and other persons who like to analyze suspicious code not to work with malware outside of a specially prepared isolated environment, from which external infrastructure is inaccessible.<\/p>\n<p><a href=\"https:\/\/www.kaspersky.com.au\/small-to-medium-business-security?icid=au_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder_______\" target=\"_blank\" rel=\"noopener\">Kaspersky products<\/a> detect elements of this attack with the following verdicts:<\/p>\n<ul>\n<li>UDS:Trojan-Downloader.Shell.FakeChecker.a<\/li>\n<li>UDS:Trojan.Python.FakeChecker.a<\/li>\n<li>HEUR:Trojan.Linux.Agent.gen<\/li>\n<li>Virus.Linux.Lamer.b<\/li>\n<li>HEUR:DoS.Linux.Agent.dt<\/li>\n<\/ul>\n<p>As for the regreSSHion vulnerability, <a href=\"https:\/\/www.kaspersky.com\/blog\/openssh-vulnerability-mitigation-cve-2024-6387-regresshion\/51603\/\" target=\"_blank\" rel=\"noopener nofollow\">as we wrote earlier<\/a>, its practical exploitation is far from being simple.<br>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kesb-trial\"><input type=\"hidden\" class=\"placeholder_for_banner\" data-cat_id=\"kesb-trial\" value=\"22278\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Someone is targeting security experts using an archive that allegedly contains an exploit for the regreSSHion vulnerability.<\/p>\n","protected":false},"author":2706,"featured_media":33820,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1999,2993,2994],"tags":[36,398,3700,268],"class_list":{"0":"post-33819","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-business","8":"category-enterprise","9":"category-smb","10":"tag-malware-2","11":"tag-patches","12":"tag-ssh","13":"tag-vulnerabilities"},"hreflang":[{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/cve-2024-6387-regresshion-researcher-attack\/33819\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/cve-2024-6387-regresshion-researcher-attack\/27675\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/cve-2024-6387-regresshion-researcher-attack\/22992\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/cve-2024-6387-regresshion-researcher-attack\/30345\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/cve-2024-6387-regresshion-researcher-attack\/27841\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/cve-2024-6387-regresshion-researcher-attack\/37815\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/cve-2024-6387-regresshion-researcher-attack\/51646\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/cve-2024-6387-regresshion-researcher-attack\/27983\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/cve-2024-6387-regresshion-researcher-attack\/33483\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com.au\/blog\/tag\/malware-2\/","name":"malware"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/posts\/33819","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/users\/2706"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/comments?post=33819"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/posts\/33819\/revisions"}],"predecessor-version":[{"id":33822,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/posts\/33819\/revisions\/33822"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/media\/33820"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/media?parent=33819"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/categories?post=33819"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/tags?post=33819"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}