Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://feeds.feedburner.com/krebsonsecurity/TEjH

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  4. xmlns:dc="http://purl.org/dc/elements/1.1/"
  5. xmlns:atom="http://www.w3.org/2005/Atom"
  6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  8. >
  9.  
  10. <channel>
  11. <title>Krebs on Security</title>
  12. <atom:link href="https://krebsonsecurity.com/feed/?" rel="self" type="application/rss+xml" />
  13. <link>https://krebsonsecurity.com</link>
  14. <description>In-depth security news and investigation</description>
  15. <lastBuildDate>Wed, 15 May 2024 12:28:20 +0000</lastBuildDate>
  16. <language>en-US</language>
  17. <sy:updatePeriod>
  18. hourly </sy:updatePeriod>
  19. <sy:updateFrequency>
  20. 1 </sy:updateFrequency>
  21. <generator>https://wordpress.org/?v=6.2.2</generator>
  22. <item>
  23. <title>Patch Tuesday, May 2024 Edition</title>
  24. <link>https://krebsonsecurity.com/2024/05/patch-tuesday-may-2024-edition/</link>
  25. <comments>https://krebsonsecurity.com/2024/05/patch-tuesday-may-2024-edition/#comments</comments>
  26. <dc:creator><![CDATA[BrianKrebs]]></dc:creator>
  27. <pubDate>Tue, 14 May 2024 20:19:23 +0000</pubDate>
  28. <category><![CDATA[Time to Patch]]></category>
  29. <category><![CDATA[acrobat]]></category>
  30. <category><![CDATA[Adobe Aero]]></category>
  31. <category><![CDATA[Adobe Animate]]></category>
  32. <category><![CDATA[Adobe Framemaker]]></category>
  33. <category><![CDATA[Adobe Substance 3D Painter]]></category>
  34. <category><![CDATA[CVE-2024-30040]]></category>
  35. <category><![CDATA[CVE-2024-30044]]></category>
  36. <category><![CDATA[CVE-2024-30051]]></category>
  37. <category><![CDATA[Google Chrome]]></category>
  38. <category><![CDATA[Illustrator]]></category>
  39. <category><![CDATA[Immersive Labs]]></category>
  40. <category><![CDATA[Kevin Breen]]></category>
  41. <category><![CDATA[macOS Sonoma 14.5 update]]></category>
  42. <category><![CDATA[MSHTML]]></category>
  43. <category><![CDATA[Qakbot]]></category>
  44. <category><![CDATA[reader]]></category>
  45. <category><![CDATA[Satnam Narang]]></category>
  46. <category><![CDATA[Sharepoint]]></category>
  47. <category><![CDATA[Tenable]]></category>
  48. <guid isPermaLink="false">https://krebsonsecurity.com/?p=67337</guid>
  49.  
  50. <description><![CDATA[Microsoft today released updates to fix more than 60 security holes in Windows computers and supported software, including two "zero-day" vulnerabilities in Windows that are already being exploited in active attacks. There are also important security patches available for macOS and Adobe users, and for the Chrome Web browser, which just patched its own zero-day flaw.]]></description>
  51. <content:encoded><![CDATA[<p><strong>Microsoft</strong> today released updates to fix more than 60 security holes in <strong>Windows</strong> computers and supported software, including two &#8220;zero-day&#8221; vulnerabilities in Windows that are already being exploited in active attacks. There are also important security patches available for <strong>macOS</strong> and <strong>Adobe</strong> users, and for the <strong>Chrome</strong> Web browser, which just patched its own zero-day flaw.</p>
  52. <p><img decoding="async" class="aligncenter wp-image-60331" src="https://krebsonsecurity.com/wp-content/uploads/2022/07/winupdatedate.png" alt="" width="749" height="496" srcset="https://krebsonsecurity.com/wp-content/uploads/2022/07/winupdatedate.png 923w, https://krebsonsecurity.com/wp-content/uploads/2022/07/winupdatedate-768x508.png 768w, https://krebsonsecurity.com/wp-content/uploads/2022/07/winupdatedate-782x518.png 782w" sizes="(max-width: 749px) 100vw, 749px" /></p>
  53. <p>First, the zero-days. <a href="https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2024-30051" target="_blank" rel="noopener">CVE-2024-30051</a> is an &#8220;elevation of privilege&#8221; bug in a core Windows library. <strong>Satnam Narang</strong> at <strong>Tenable</strong> said this flaw is being used as part of post-compromise activity to elevate privileges as a local attacker.</p>
  54. <p>&#8220;CVE-2024-30051 is used to gain initial access into a target environment and requires the use of social engineering tactics via email, social media or instant messaging to convince a target to open a specially crafted document file,&#8221; Narang said. &#8220;Once exploited, the attacker can bypass OLE mitigations in Microsoft 365 and Microsoft Office, which are security features designed to protect end users from malicious files.&#8221;</p>
  55. <p><strong>Kaspersky Lab</strong>, one of two companies credited with reporting exploitation of CVE-2024-30051 to Microsoft, has published <a href="https://securelist.com/cve-2024-30051/112618/" target="_blank" rel="noopener">a fascinating writeup</a> on how they discovered the exploit in a file shared with Virustotal.com.</p>
  56. <p>Kaspersky said it has since seen the exploit used together with <a href="https://krebsonsecurity.com/2023/08/u-s-hacks-qakbot-quietly-removes-botnet-infections/" target="_blank" rel="noopener">QakBot</a> and other malware. Emerging in 2007 as a banking trojan, QakBot (a.k.a. <strong>Qbot</strong> and <strong>Pinkslipbot</strong>) has morphed into an advanced malware strain now used by multiple cybercriminal groups to prepare newly compromised networks for ransomware infestations.</p>
  57. <p><a href="https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2024-30040" target="_blank" rel="noopener">CVE-2024-30040</a> is a security feature bypass in <strong>MSHTML</strong>, a component that is deeply tied to the default Web browser on Windows systems. Microsoft&#8217;s advisory on this flaw is fairly sparse, but <strong>Kevin Breen</strong> from <strong>Immersive Labs</strong> said this vulnerability also affects <strong>Office 365</strong> and <strong>Microsoft Office</strong> applications.</p>
  58. <p>&#8220;Very little information is provided and the short description is painfully obtuse,&#8221; Breen said of Microsoft&#8217;s advisory on CVE-2024-30040.</p>
  59. <p><span id="more-67337"></span></p>
  60. <p>The only vulnerability fixed this month that earned Microsoft&#8217;s most-dire &#8220;critical&#8221; rating is <a href="https://msrc.microsoft.com/update-guide/en-US/advisory/CVE-2024-30044" target="_blank" rel="noopener">CVE-2024-30044</a>, a flaw in <strong>Sharepoint</strong> that Microsoft said is likely to be exploited. Tenable&#8217;s Narang notes that exploitation of this bug requires an attacker to be authenticated to a vulnerable SharePoint Server with Site Owner permissions (or higher) first and to take additional steps in order to exploit this flaw, which makes this flaw less likely to be widely exploited as most attackers follow the path of least resistance.</p>
  61. <p>Five days ago, Google <a href="https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_9.html" target="_blank" rel="noopener">released a security update for Chrome</a> that fixes a zero-day in the popular browser. Chrome usually auto-downloads any available updates, but it still may require a complete restart of the browser to install them. If you use Chrome and see a &#8220;Relaunch to update&#8221; message in the upper right corner of the browser, it&#8217;s time to restart.</p>
  62. <p>Apple has just shipped <a href="https://support.apple.com/en-us/HT214106" target="_blank" rel="noopener">macOS Sonoma 14.5 update</a>, which includes nearly two dozen security patches. To ensure your Mac is up-to-date, go to System Settings, General tab, then Software Update and follow any prompts.</p>
  63. <p>Finally, Adobe has <a href="https://helpx.adobe.com/security.html" target="_blank" rel="noopener">critical security patches available</a> for a range of products, including <strong>Acrobat, Reader</strong>, <strong>Illustrator</strong>, <strong>Adobe Substance 3D Painter</strong>, <strong>Adobe Aero</strong>, <strong>Adobe Animate</strong> and <strong>Adobe Framemaker</strong>.</p>
  64. <p>Regardless of whether you use a Mac or Windows system (or something else), it&#8217;s always a good idea to backup your data and or system before applying any security updates. For a closer look at the individual fixes released by Microsoft today, check out the complete list over at the <a href="https://isc.sans.edu/forums/diary/Microsoft%20May%202024%20Patch%20Tuesday/30920/" target="_blank" rel="noopener">SANS Internet Storm Center</a>. Anyone in charge of maintaining Windows systems in an enterprise environment should keep an eye on <a href="http://askwoody.com" target="_blank" rel="noopener">askwoody.com</a>, which usually has the scoop on any wonky Windows patches.</p>
  65. <p>Update, May 15, 8:28 a.m.: Corrected misattribution of CVE-2024-30051.</p>
  66. ]]></content:encoded>
  67. <wfw:commentRss>https://krebsonsecurity.com/2024/05/patch-tuesday-may-2024-edition/feed/</wfw:commentRss>
  68. <slash:comments>9</slash:comments>
  69. </item>
  70. <item>
  71. <title>How Did Authorities Identify the Alleged Lockbit Boss?</title>
  72. <link>https://krebsonsecurity.com/2024/05/how-did-authorities-identify-the-alleged-lockbit-boss/</link>
  73. <comments>https://krebsonsecurity.com/2024/05/how-did-authorities-identify-the-alleged-lockbit-boss/#comments</comments>
  74. <dc:creator><![CDATA[BrianKrebs]]></dc:creator>
  75. <pubDate>Mon, 13 May 2024 11:26:27 +0000</pubDate>
  76. <category><![CDATA[A Little Sunshine]]></category>
  77. <category><![CDATA[Breadcrumbs]]></category>
  78. <category><![CDATA[Ne'er-Do-Well News]]></category>
  79. <category><![CDATA[Ransomware]]></category>
  80. <category><![CDATA[3k@xakep.ru]]></category>
  81. <category><![CDATA[7.9521020220]]></category>
  82. <category><![CDATA[antichat]]></category>
  83. <category><![CDATA[Cerber]]></category>
  84. <category><![CDATA[Constella Intelligence]]></category>
  85. <category><![CDATA[d.horoshev@gmail.com]]></category>
  86. <category><![CDATA[Dmitrij Ju Horoshev]]></category>
  87. <category><![CDATA[Dmitry Yuriyevich Khoroshev]]></category>
  88. <category><![CDATA[exploit]]></category>
  89. <category><![CDATA[ICQ number 669316]]></category>
  90. <category><![CDATA[Intel 471]]></category>
  91. <category><![CDATA[khoroshev1@icloud.com]]></category>
  92. <category><![CDATA[LockBit]]></category>
  93. <category><![CDATA[LockBitSupp]]></category>
  94. <category><![CDATA[NeroWolfe]]></category>
  95. <category><![CDATA[pin@darktower.su]]></category>
  96. <category><![CDATA[Putinkrab]]></category>
  97. <category><![CDATA[ransomware-as-a-service]]></category>
  98. <category><![CDATA[sitedev5@yandex.ru]]></category>
  99. <category><![CDATA[stairwell.ru]]></category>
  100. <category><![CDATA[tkaner.com]]></category>
  101. <category><![CDATA[U.S. Department of the Treasury]]></category>
  102. <category><![CDATA[Verified]]></category>
  103. <guid isPermaLink="false">https://krebsonsecurity.com/?p=67396</guid>
  104.  
  105. <description><![CDATA[Last week, the United States joined the U.K. and Australia in sanctioning and charging a Russian man named Dmitry Yuryevich Khoroshev as the leader of the infamous LockBit ransomware group. LockBit's leader "LockBitSupp" claims the feds named the wrong guy, saying the charges don't explain how they connected him to Khoroshev. This post examines the activities of Khoroshev's many alter egos on the cybercrime forums, and tracks the career of a gifted malware author who has written and sold malicious code for the past 14 years.]]></description>
  106. <content:encoded><![CDATA[<p>Last week, the United States joined the U.K. and Australia in sanctioning and charging a Russian man named <strong>Dmitry Yuryevich Khoroshev</strong> as the leader of the infamous <strong>LockBit</strong> ransomware group. LockBit&#8217;s leader &#8220;<strong>LockBitSupp</strong>&#8221; claims the feds named the wrong guy, saying the charges don&#8217;t explain how they connected him to Khoroshev. This post examines the activities of Khoroshev&#8217;s many alter egos on the cybercrime forums, and tracks the career of a gifted malware author who has written and sold malicious code for the past 14 years.</p>
  107. <div id="attachment_67453" style="width: 260px" class="wp-caption alignright"><img aria-describedby="caption-attachment-67453" decoding="async" loading="lazy" class=" wp-image-67453" src="https://krebsonsecurity.com/wp-content/uploads/2024/05/khoroshev-sq.png" alt="" width="250" height="255" /><p id="caption-attachment-67453" class="wp-caption-text">Dmitry Yuryevich Khoroshev. Image: treasury.gov.</p></div>
  108. <p>On May 7, the U.S. Department of Justice <a href="https://www.justice.gov/opa/media/1350921/dl?inline" target="_blank" rel="noopener">indicted</a> Khoroshev on 26 criminal counts, including extortion, wire fraud, and conspiracy. The government alleges Khoroshev created, sold and used the LockBit ransomware strain to personally extort more than $100 million from hundreds of victim organizations, and that LockBit as a group extorted roughly half a billion dollars over four years.</p>
  109. <p>Federal investigators say Khoroshev ran LockBit as a &#8220;<strong>ransomware-as-a-service</strong>&#8221; operation, wherein he kept 20 percent of any ransom amount paid by a victim organization infected with his code, with the remaining 80 percent of the payment going to LockBit affiliates responsible for spreading the malware.</p>
  110. <p>Financial <a href="https://ofac.treasury.gov/recent-actions/20240507" target="_blank" rel="noopener">sanctions levied against Khoroshev</a> by the <strong>U.S. Department of the Treasury</strong> listed his known email and street address (in Voronezh, in southwest Russia), passport number, and even his tax ID number (hello, Russian tax authorities). The Treasury filing says Khoroshev used the emails <strong>sitedev5@yandex.ru</strong>, and <strong>khoroshev1@icloud.com</strong>.</p>
  111. <p>According to <a href="https://www.domaintools.com" target="_blank" rel="noopener">DomainTools.com</a>, the address sitedev5@yandex.ru was used to register at least six domains, including a Russian business registered in Khoroshev&#8217;s name called <strong>tkaner.com</strong>, which is a blog about clothing and fabrics.</p>
  112. <p>A search at the breach-tracking service <a href="https://constella.ai" target="_blank" rel="noopener">Constella Intelligence</a> on the phone number in Tkaner&#8217;s registration records  &#8212; <strong>7.9521020220</strong> &#8212; brings up multiple official Russian government documents listing the number&#8217;s owner as Dmitri Yurievich Khoroshev.</p>
  113. <p>Another domain registered to that phone number was <strong>stairwell[.]ru</strong>, which at one point advertised the sale of wooden staircases. Constella finds that the email addresses webmaster@stairwell.ru and admin@stairwell.ru used the password <strong>225948</strong>.</p>
  114. <p>DomainTools reports that stairwell.ru for several years included the registrant&#8217;s name as &#8220;<strong>Dmitrij Ju Horoshev</strong>,&#8221; and the email address <strong>pin@darktower.su</strong>. According to Constella, this email address was used in 2010 to register an account for a Dmitry Yurievich Khoroshev from Voronezh, Russia at the hosting provider <strong>firstvds.ru</strong>.</p>
  115. <div id="attachment_67416" style="width: 760px" class="wp-caption aligncenter"><img aria-describedby="caption-attachment-67416" decoding="async" loading="lazy" class=" wp-image-67416" src="https://krebsonsecurity.com/wp-content/uploads/2024/05/voronezh.png" alt="" width="750" height="499" srcset="https://krebsonsecurity.com/wp-content/uploads/2024/05/voronezh.png 800w, https://krebsonsecurity.com/wp-content/uploads/2024/05/voronezh-768x511.png 768w, https://krebsonsecurity.com/wp-content/uploads/2024/05/voronezh-782x520.png 782w" sizes="(max-width: 750px) 100vw, 750px" /><p id="caption-attachment-67416" class="wp-caption-text">Image: Shutterstock.</p></div>
  116. <p>Cyber intelligence firm <a href="https://www.intel471.com" target="_blank" rel="noopener">Intel 471</a> finds that pin@darktower.ru was used by a Russian-speaking member called Pin on the English-language cybercrime forum <b>Opensc. </b>Pin was active on Opensc around March 2012, and authored 13 posts that mostly concerned data encryption issues, or how to fix bugs in code.</p>
  117. <p>Other posts concerned custom code Pin claimed to have written that would bypass memory protections on Windows XP and Windows 7 systems, and inject malware into memory space normally allocated to trusted applications on a Windows machine.</p>
  118. <p>Pin also was active at that same time on the Russian-language security forum <b>Antichat</b>, where they told fellow forum members to contact them at the ICQ instant messenger number <strong>669316</strong>.</p>
  119. <h2>NEROWOLFE</h2>
  120. <p>A search on the ICQ number 669316 at Intel 471 shows that in April 2011, a user by the name <strong>NeroWolfe</strong> joined the Russian cybercrime forum <strong>Zloy</strong> using the email address <strong>d.horoshev@gmail.com</strong>, and from an Internet address in Voronezh, RU.</p>
  121. <p>Constella finds the same password tied to webmaster@stairwell.ru (225948) was used by the email address <strong>3k@xakep.ru</strong>, which Intel 471 says was registered to more than a dozen NeroWolfe accounts across just as many Russian cybercrime forums between 2011 and 2015.</p>
  122. <p>NeroWolfe&#8217;s introductory post to the forum <strong>Verified</strong> in Oct. 2011 said he was a system administrator and C++ coder.</p>
  123. <p>&#8220;Installing SpyEYE, ZeuS, any DDoS and spam admin panels,&#8221; NeroWolfe wrote. This user said they specialize in developing malware, creating computer worms, and crafting new ways to hijack Web browsers.</p>
  124. <p><img decoding="async" loading="lazy" class="aligncenter wp-image-53514" src="https://krebsonsecurity.com/wp-content/uploads/2020/11/ransomware.png" alt="" width="750" height="562" srcset="https://krebsonsecurity.com/wp-content/uploads/2020/11/ransomware.png 1016w, https://krebsonsecurity.com/wp-content/uploads/2020/11/ransomware-768x575.png 768w" sizes="(max-width: 750px) 100vw, 750px" /></p>
  125. <p>&#8220;I can provide my portfolio on request,&#8221; NeroWolfe wrote. &#8220;P.S. I don&#8217;t modify someone else&#8217;s code or work with someone else&#8217;s frameworks.&#8221;</p>
  126. <p>In April 2013, NeroWolfe wrote in a private message to another Verified forum user that he was selling a malware &#8220;loader&#8221; program that could bypass all of the security protections on Windows XP and Windows 7.</p>
  127. <p>&#8220;The access to the network is slightly restricted,&#8221; NeroWolfe said of the loader, which he was selling for $5,000. &#8220;You won&#8217;t manage to bind a port. However, it&#8217;s quite possible to send data. The code is written in C.&#8221;</p>
  128. <p>In an October 2013 discussion on the cybercrime forum <strong>Exploit</strong>, NeroWolfe weighed in on the karmic ramifications of ransomware. At the time, ransomware-as-a-service didn&#8217;t exist yet, and many members of Exploit were still making good money from &#8220;lockers,&#8221; relatively crude programs that locked the user out of their system until they agreed to make a small payment (usually a few hundred dollars via prepaid Green Dot cards).</p>
  129. <p>Lockers, which presaged the coming ransomware scourge, were generally viewed by the Russian-speaking cybercrime forums as harmless moneymaking opportunities, because they usually didn&#8217;t seek to harm the host computer or endanger files on the system. Also, there were still plenty of locker programs that aspiring cybercriminals could either buy or rent to make a steady income.</p>
  130. <p>NeroWolfe reminded forum denizens that they were just as vulnerable to ransomware attacks as their would-be victims, and that what goes around comes around.</p>
  131. <p>&#8220;Guys, do you have a conscience?,&#8221; NeroWolfe wrote. &#8220;Okay, lockers, network gopstop aka business in Russian. The last thing was always squeezed out of the suckers. But encoders, no one is protected from them, including the local audience.&#8221;<span id="more-67396"></span></p>
  132. <p>If Khoroshev was ever worried that someone outside of Russia might be able to connect his early hacker handles to his real life persona, that&#8217;s not clear from reviewing his history online. In fact, the same email address tied to so many of NeroWolfe&#8217;s accounts on the forums &#8212; 3k@xakep.ru &#8212; was used in 2011 to create an account for a Dmitry Yurevich Khoroshev on the Russian social media network <strong>Vkontakte</strong>.</p>
  133. <p>NeroWolfe seems to have abandoned all of his forum accounts sometime in 2016. In November 2016, an exploit[.]ru member filed an official complaint against NeroWolfe, saying NeroWolfe had been paid $2,000 to produce custom code but never finished the project and vanished.</p>
  134. <p>It&#8217;s unclear what happened to NeroWolfe or to Khoroshev during this time. Maybe he got arrested, or some close associates did. Perhaps he just decided it was time to lay low and hit the reset on his operational security efforts, given his past failures in this regard. It&#8217;s also possible NeroWolfe landed a real job somewhere for a few years, fathered a child, and/or had to put his cybercrime career on hold.</p>
  135. <h2>PUTINKRAB</h2>
  136. <p>Or perhaps Khoroshev saw the coming ransomware industry for the endless pot of gold that it was about to become, and then dedicated himself to working on custom ransomware code. That&#8217;s what the government believes.</p>
  137. <p>The indictment against Khoroshev says he used the hacker nickname <strong>Putinkrab</strong>, and Intel 471 says this corresponds to a username that was first registered across three major Russian cybercrime forums in early 2019.</p>
  138. <p>KrebsOnSecurity could find no obvious connections between Putinkrab and any of Khoroshev&#8217;s older identities. However, if Putinkrab was Khoroshev, he would have learned from his past mistakes and started fresh with a new identity (which he did). But also, it is likely the government hasn&#8217;t shared all of the intelligence it has collected against him (more on that in a bit).</p>
  139. <p>Putinkrab&#8217;s first posts on the Russian cybercrime forums XSS, Exploit and UFOLabs saw this user selling ransomware source code written in C.</p>
  140. <div id="attachment_67402" style="width: 795px" class="wp-caption aligncenter"><img aria-describedby="caption-attachment-67402" decoding="async" loading="lazy" class="size-full wp-image-67402" src="https://krebsonsecurity.com/wp-content/uploads/2024/05/putinkrab-ufo.png" alt="" width="785" height="849" srcset="https://krebsonsecurity.com/wp-content/uploads/2024/05/putinkrab-ufo.png 785w, https://krebsonsecurity.com/wp-content/uploads/2024/05/putinkrab-ufo-768x831.png 768w, https://krebsonsecurity.com/wp-content/uploads/2024/05/putinkrab-ufo-782x846.png 782w" sizes="(max-width: 785px) 100vw, 785px" /><p id="caption-attachment-67402" class="wp-caption-text">A machine-translated ad for ransomware source code from Putinkrab on the Russian language cybercrime forum UFOlabs in 2019. Image: Ke-la.com.</p></div>
  141. <p>In April 2019, Putkinkrab offered an affiliate program that would run on top of his custom-made ransomware code.</p>
  142. <p>&#8220;I want to work for a share of the ransoms: 20/80,&#8221; Putinkrab wrote on Exploit. &#8220;20 percent is my percentage for the work, you get 80% of the ransoms. The percentage can be reduced up to 10/90 if the volumes are good. But now, temporarily, until the service is fully automated, we are working using a different algorithm.&#8221;</p>
  143. <p>Throughout the summer of 2019, Putinkrab posted multiple updates to Exploit about new features being added to his ransomware strain, as well as novel evasion techniques to avoid detection by security tools. He also told forum members he was looking for investors for a new ransomware project based on his code.</p>
  144. <p>In response to an Exploit member who complained that the security industry was making it harder to profit from ransomware, Putinkrab said that was because so many cybercriminals were relying on crappy ransomware code.</p>
  145. <p>&#8220;The vast majority of top antiviruses have acquired behavioral analysis, which blocks 95% of crypto-lockers at their root,&#8221; Putinkrab wrote. &#8220;Cryptolockers made a lot of noise in the press, but lazy system administrators don’t make backups after that. The vast majority of cryptolockers are written by people who have little understanding of cryptography. Therefore, decryptors appear on the Internet, and with them the hope that files can be decrypted without paying a ransom. They just sit and wait. Contact with the owner of the key is lost over time.&#8221;</p>
  146. <p>Putinkrab said he had every confidence his ransomware code was a game-changer, and a huge money machine.</p>
  147. <p>&#8220;The game is just gaining momentum,&#8221; Putinkrab wrote. &#8220;Weak players lose and are eliminated.&#8221;</p>
  148. <p>The rest of his response was structured like a poem:</p>
  149. <blockquote><p>&#8220;In this world, the strongest survive.<br />
  150. Our life is just a struggle.<br />
  151. The winner will be the smartest,<br />
  152. Who has his head on his shoulders.&#8221;</p></blockquote>
  153. <p>Putinkrab&#8217;s final post came on August 23, 2019. The Justice Department says the LockBit ransomware affiliate program was officially launched five months later. From there on out, the government says, Khoroshev adopted the persona of LockBitSupp. In his introductory post on Exploit, LockBit&#8217;s mastermind said the ransomware strain had been in development since September 2019.</p>
  154. <p>The original LockBit malware was written in C (a language that NeroWolfe excelled at). Here&#8217;s the original description of LockBit, from its maker:</p>
  155. <blockquote><p>&#8220;The software is written in C and Assembler; encryption is performed through the I/O Completion Port; there is a port scanning local networks and an option to find all DFS, SMB, WebDAV network shares, an admin panel in Tor, automatic test decryption; a decryption tool is provided; there is a chat with Push notifications, a Jabber bot that forwards correspondence and an option to terminate services/processes in line which prevent the ransomware from opening files at a certain moment. The ransomware sets file permissions and removes blocking attributes, deletes shadow copies, clears logs and mounts hidden partitions; there is an option to drag-and-drop files/folders and a console/hidden mode. The ransomware encrypts files in parts in various places: the larger the file size, the more parts there are. The algorithms used are AES + RSA.</p>
  156. <p>You are the one who determines the ransom amount after communicating with the victim. The ransom paid in any currency that suits you will be transferred to your wallets. The Jabber bot serves as an admin panel and is used for banning, providing decryption tools, chatting &#8211; Jabber is used for absolutely everything.&#8221;</p></blockquote>
  157. <h2>CONCLUSION</h2>
  158. <p>Does the above timeline prove that NeroWolfe/Khoroshev is LockBitSupp? No. However, it does indicate Khoroshev was for many years deeply invested in countless schemes involving botnets, stolen data, and malware he wrote that others used to great effect. NeroWolfe&#8217;s many private messages from fellow forum members confirm this.</p>
  159. <p>NeroWolfe&#8217;s specialty was creating custom code that employed novel stealth and evasion techniques, and he was always quick to volunteer his services on the forums whenever anyone was looking help on a malware project that called for a strong C or C++ programmer.</p>
  160. <p>Someone with those qualifications &#8212; as well as demonstrated mastery of data encryption and decryption techniques &#8212; would have been in great demand by the ransomware-as-a-service industry that took off at around the same time NeroWolfe vanished from the forums.</p>
  161. <p>Someone like that who is near or at the top of their game vis-a-vis their peers does not simply walk away from that level of influence, community status, and potential income stream unless forced to do so by circumstances beyond their immediate control.</p>
  162. <p>It&#8217;s important to note that Putinkrab didn&#8217;t just materialize out of thin air in 2019 &#8212; suddenly endowed with knowledge about how to write advanced, stealthy ransomware strains. That knowledge clearly came from someone who&#8217;d already had years of experience building and deploying ransomware strains against real-life victim organizations.</p>
  163. <p>Thus, whoever Putinkrab was before they adopted that moniker, it&#8217;s a safe bet they were involved in the development and use of earlier, highly successful ransomware strains. One strong possible candidate is <a href="https://blog.malwarebytes.com/detections/ransom-cerber/" target="_blank" rel="noopener noreferrer">Cerber ransomware</a>, the most popular and effective affiliate program operating between early 2016 and mid-2017. Cerber thrived because it emerged as an early mover in the market for ransomware-as-a-service offerings.</p>
  164. <p>In February 2024, <a href="https://krebsonsecurity.com/2024/02/feds-seize-lockbit-ransomware-websites-offer-decryption-tools-troll-affiliates/" target="_blank" rel="noopener">the FBI seized LockBit&#8217;s cybercrime infrastructure on the dark web</a>, following an apparently lengthy infiltration of the group&#8217;s operations. The United States has already indicted and sanctioned at least five other alleged LockBit ringleaders or affiliates, so presumably the feds have been able to draw additional resources from those investigations.</p>
  165. <p>Also, it seems likely that the three national intelligence agencies involved in bringing these charges are not showing all of their cards. For example, the Treasury documents on Khoroshev mention a single cryptocurrency address, and yet experts interviewed for this story say there are no obvious clues connecting this address to Khoroshev or Putinkrab.</p>
  166. <p>But given that LockBitSupp has been actively involved in Lockbit ransomware attacks against organizations for four years now, the government almost certainly has an extensive list of the LockBit leader&#8217;s various cryptocurrency addresses &#8212; and probably even his bank accounts in Russia. And no doubt the money trail from some of those transactions was traceable to its ultimate beneficiary (or close enough).</p>
  167. <p>Not long after Khoroshev was charged as the leader of LockBit, a number of open-source intelligence accounts on Telegram began extending the information released by the Treasury Department. Within hours, these sleuths had unearthed more than a dozen credit card accounts used by Khoroshev over the past decade, as well as his various bank account numbers in Russia.</p>
  168. <p>The point is, this post is based on data that&#8217;s available to and verifiable by KrebsOnSecurity. Woodward &amp; Bernstein&#8217;s source in the Watergate investigation &#8212; Deep Throat &#8212; famously told the two reporters to &#8220;follow the money.&#8221; This is always excellent advice. But these days, that can be a lot easier said than done &#8212; especially with people who a) do not wish to be found, and b) don&#8217;t exactly file annual reports.</p>
  169. ]]></content:encoded>
  170. <wfw:commentRss>https://krebsonsecurity.com/2024/05/how-did-authorities-identify-the-alleged-lockbit-boss/feed/</wfw:commentRss>
  171. <slash:comments>9</slash:comments>
  172. </item>
  173. <item>
  174. <title>U.S. Charges Russian Man as Boss of LockBit Ransomware Group</title>
  175. <link>https://krebsonsecurity.com/2024/05/u-s-charges-russian-man-as-boss-of-lockbit-ransomware-group/</link>
  176. <comments>https://krebsonsecurity.com/2024/05/u-s-charges-russian-man-as-boss-of-lockbit-ransomware-group/#comments</comments>
  177. <dc:creator><![CDATA[BrianKrebs]]></dc:creator>
  178. <pubDate>Tue, 07 May 2024 17:36:14 +0000</pubDate>
  179. <category><![CDATA[A Little Sunshine]]></category>
  180. <category><![CDATA[Ne'er-Do-Well News]]></category>
  181. <category><![CDATA[Russia's War on Ukraine]]></category>
  182. <category><![CDATA[Dmitry Yuryevich Khoroshev]]></category>
  183. <category><![CDATA[LockBitSupp]]></category>
  184. <category><![CDATA[U.S. Attorney Philip R. Sellinger]]></category>
  185. <category><![CDATA[U.S. Department of Justice]]></category>
  186. <category><![CDATA[Дмитрий Юрьевич Хорошев]]></category>
  187. <guid isPermaLink="false">https://krebsonsecurity.com/?p=67380</guid>
  188.  
  189. <description><![CDATA[The United States joined the United Kingdom and Australia today in sanctioning 31-year-old Russian national Dmitry Yuryevich Khoroshev as the alleged leader of the infamous ransomware group LockBit. The U.S. Department of Justice also indicted Khoroshev as the gang's leader "LockbitSupp," and charged him with using Lockbit to attack more than 2,000 victims and extort at least $100 million in ransomware payments.]]></description>
  190. <content:encoded><![CDATA[<p>The United States joined the United Kingdom and Australia today in sanctioning 31-year-old Russian national <strong>Dmitry Yuryevich Khoroshev</strong> as the alleged leader of the infamous ransomware group <strong>LockBit</strong>. The <strong>U.S. Department of Justice</strong> also indicted Khoroshev and charged him with using Lockbit to attack more than 2,000 victims and extort at least $100 million in ransomware payments.</p>
  191. <div id="attachment_67385" style="width: 760px" class="wp-caption aligncenter"><img aria-describedby="caption-attachment-67385" decoding="async" loading="lazy" class=" wp-image-67385" src="https://krebsonsecurity.com/wp-content/uploads/2024/05/lockbitsupp-nca.png" alt="" width="750" height="526" srcset="https://krebsonsecurity.com/wp-content/uploads/2024/05/lockbitsupp-nca.png 1174w, https://krebsonsecurity.com/wp-content/uploads/2024/05/lockbitsupp-nca-768x538.png 768w, https://krebsonsecurity.com/wp-content/uploads/2024/05/lockbitsupp-nca-782x548.png 782w, https://krebsonsecurity.com/wp-content/uploads/2024/05/lockbitsupp-nca-100x70.png 100w" sizes="(max-width: 750px) 100vw, 750px" /><p id="caption-attachment-67385" class="wp-caption-text">Image: U.K. National Crime Agency.</p></div>
  192. <p>Khoroshev (Дмитрий Юрьевич Хорошев), a resident of Voronezh, Russia, was charged in <a href="https://www.justice.gov/opa/media/1350921/dl?inline" target="_blank" rel="noopener">a 26-count indictment</a> by a grand jury in New Jersey.</p>
  193. <p>&#8220;Dmitry Khoroshev conceived, developed, and administered Lockbit, the most prolific ransomware variant and group in the world, enabling himself and his affiliates to wreak havoc and cause billions of dollars in damage to thousands of victims around the globe,&#8221; <strong>U.S. Attorney Philip R. Sellinger</strong> said in <a href="https://www.justice.gov/opa/pr/us-charges-russian-national-developing-and-operating-lockbit-ransomware" target="_blank" rel="noopener">a statement</a> released by the Justice Department.</p>
  194. <p>The indictment alleges Khoroshev acted as the LockBit ransomware group’s developer and administrator from its inception in September 2019 through May 2024, and that he typically received a 20 percent share of each ransom payment extorted from LockBit victims.</p>
  195. <p>The government says LockBit victims included individuals, small businesses, multinational corporations, hospitals, schools, nonprofit organizations, critical infrastructure, and government and law-enforcement agencies.</p>
  196. <p>&#8220;Khoroshev and his co-conspirators extracted at least $500 million in ransom payments from their victims and caused billions of dollars in broader losses, such as lost revenue, incident response, and recovery,&#8221; the DOJ said. &#8220;The LockBit ransomware group attacked more than 2,500 victims in at least 120 countries, including 1,800 victims in the United States.&#8221;</p>
  197. <p>The <a href="https://www.nationalcrimeagency.gov.uk/news/lockbit-leader-unmasked-and-sanctioned" target="_blank" rel="noopener">unmasking of LockBitSupp</a> comes nearly three months after U.S. and U.K. authorities seized the darknet websites run by LockBit, retrofitting it with press releases about the law enforcement action and <a href="https://www.nomoreransom.org/en/decryption-tools.html" target="_blank" rel="noopener">free tools</a> to help LockBit victims decrypt infected systems.</p>
  198. <div id="attachment_66436" style="width: 759px" class="wp-caption aligncenter"><img aria-describedby="caption-attachment-66436" decoding="async" loading="lazy" class=" wp-image-66436" src="https://krebsonsecurity.com/wp-content/uploads/2024/02/lockbitseized.png" alt="" width="749" height="474" srcset="https://krebsonsecurity.com/wp-content/uploads/2024/02/lockbitseized.png 1379w, https://krebsonsecurity.com/wp-content/uploads/2024/02/lockbitseized-768x486.png 768w, https://krebsonsecurity.com/wp-content/uploads/2024/02/lockbitseized-782x494.png 782w" sizes="(max-width: 749px) 100vw, 749px" /><p id="caption-attachment-66436" class="wp-caption-text">The feds used the existing design on LockBit&#8217;s victim shaming website to feature press releases and free decryption tools.</p></div>
  199. <p>One of the blog captions that authorities left on the seized site was a teaser page that read, &#8220;Who is LockbitSupp?,&#8221; which promised to reveal the true identity of the ransomware group leader. That item featured a countdown clock until the big reveal, but when the site&#8217;s timer expired no such details were offered.</p>
  200. <p>Following the FBI&#8217;s raid, LockBitSupp took to Russian cybercrime forums to assure his partners and affiliates that the ransomware operation was still fully operational. LockBitSupp also raised another set of darknet websites that soon promised to release data stolen from a number of LockBit victims ransomed prior to the FBI raid.</p>
  201. <p>One of the victims LockBitSupp continued extorting was Fulton County, Ga. Following the FBI raid, LockbitSupp <a href="https://krebsonsecurity.com/2024/03/blackcat-ransomware-group-implodes-after-apparent-22m-ransom-payment-by-change-healthcare/" target="_blank" rel="noopener">vowed to release sensitive documents stolen from the county court system</a> unless paid a ransom demand before LockBit&#8217;s countdown timer expired. But when Fulton County officials <a href="https://krebsonsecurity.com/2024/02/fulton-county-security-experts-call-lockbits-bluff/" target="_blank" rel="noopener">refused to pay</a> and the timer expired, no stolen records were ever published. Experts said it was likely the FBI had in fact seized all of LockBit&#8217;s stolen data.</p>
  202. <p>LockBitSupp also bragged that their real identity would never be revealed, and at one point offered to pay $10 million to anyone who could discover their real name.</p>
  203. <p>KrebsOnSecurity has been in intermittent contact with LockBitSupp for several months over the course of reporting on different LockBit victims. Reached at the same ToX instant messenger identity that the ransomware group leader has promoted on Russian cybercrime forums, LockBitSupp claimed the authorities named the wrong guy.</p>
  204. <p><span class="pullquote pqright">&#8220;It&#8217;s not me,&#8221; LockBitSupp replied in Russian. &#8220;I don&#8217;t understand how the FBI was able to connect me with this poor guy.</span> Where is the logical chain that it is me? Don&#8217;t you feel sorry for a random innocent person?&#8221;</p>
  205. <p>LockBitSupp, who now has a $10 million bounty for his arrest from the <strong>U.S. Department of State</strong>, has been known to be flexible with the truth. The Lockbit group routinely practiced &#8220;double extortion&#8221; against its victims &#8212; requiring one ransom payment for a key to unlock hijacked systems, and a separate payment in exchange for a promise to delete data stolen from its victims.</p>
  206. <p>But Justice Department officials say LockBit never deleted its victim data, regardless of whether those organizations paid a ransom to keep the information from being published on LockBit&#8217;s victim shaming website.<span id="more-67380"></span></p>
  207. <p>Khoroshev is the sixth person officially indicted as active members of LockBit. The government says Russian national <strong>Artur Sungatov</strong> used LockBit ransomware against victims in manufacturing, logistics, insurance and other companies throughout the United States.</p>
  208. <p><strong>Ivan Gennadievich Kondratyev</strong>, a.k.a. “Bassterlord,” allegedly deployed LockBit against targets in the United States, Singapore, Taiwan, and Lebanon. Kondratyev is also <a href="https://krebsonsecurity.com/wp-content/uploads/2024/02/vasiliev.pdf" target="_blank" rel="noopener">charged</a> (PDF) with three criminal counts arising from his alleged use of the Sodinokibi (aka “<a href="https://krebsonsecurity.com/?s=revil" target="_blank" rel="noopener">REvil</a>“) ransomware variant to encrypt data, exfiltrate victim information, and extort a ransom payment from a corporate victim based in Alameda County, California.</p>
  209. <p>In May 2023, U.S. authorities unsealed indictments against two alleged LockBit affiliates, <strong>Mikhail “Wazawaka” Matveev</strong> and <strong>Mikhail Vasiliev</strong>. In January 2022, KrebsOnSecurity published <a href="https://krebsonsecurity.com/2022/01/who-is-the-network-access-broker-wazawaka/" target="_blank" rel="noopener">Who is the Network Access Broker ‘Wazawaka,’</a> which followed clues from Wazawaka’s many pseudonyms and contact details on the Russian-language cybercrime forums back to a 31-year-old Mikhail Matveev from Abaza, RU.</p>
  210. <p>Matveev remains at large, presumably still in Russia. Meanwhile, the U.S. Department of State has <a href="http://www.tips.fbi.gov/" target="_blank" rel="noopener">a standing $10 million reward offer</a> for information leading to Matveev&#8217;s arrest.</p>
  211. <p>Vasiliev, 35, of Bradford, Ontario, Canada, is in custody in Canada awaiting extradition to the United States (the complaint against Vasiliev is at <a href="https://krebsonsecurity.com/wp-content/uploads/2024/02/vasiliev.pdf" target="_blank" rel="noopener">this PDF</a>).</p>
  212. <p>In June 2023, Russian national <strong>Ruslan Magomedovich Astamirov</strong> was charged in New Jersey for his participation in the LockBit conspiracy, including the deployment of LockBit against victims in Florida, Japan, France, and Kenya. Astamirov is currently in custody in the United States awaiting trial.</p>
  213. <p>The Justice Department is urging victims targeted by LockBit to contact the FBI at <a class="ext" href="https://lockbitvictims.ic3.gov/" target="_blank" rel="noopener" data-extlink="">https://lockbitvictims.ic3.gov/</a> to file an official complaint, and to determine whether affected systems can be successfully decrypted.</p>
  214. ]]></content:encoded>
  215. <wfw:commentRss>https://krebsonsecurity.com/2024/05/u-s-charges-russian-man-as-boss-of-lockbit-ransomware-group/feed/</wfw:commentRss>
  216. <slash:comments>16</slash:comments>
  217. </item>
  218. <item>
  219. <title>Why Your VPN May Not Be As Secure As It Claims</title>
  220. <link>https://krebsonsecurity.com/2024/05/why-your-vpn-may-not-be-as-secure-as-it-claims/</link>
  221. <comments>https://krebsonsecurity.com/2024/05/why-your-vpn-may-not-be-as-secure-as-it-claims/#comments</comments>
  222. <dc:creator><![CDATA[BrianKrebs]]></dc:creator>
  223. <pubDate>Mon, 06 May 2024 14:24:47 +0000</pubDate>
  224. <category><![CDATA[A Little Sunshine]]></category>
  225. <category><![CDATA[Latest Warnings]]></category>
  226. <category><![CDATA[The Coming Storm]]></category>
  227. <category><![CDATA[Web Fraud 2.0]]></category>
  228. <category><![CDATA[Bill Woodcock]]></category>
  229. <category><![CDATA[Dani Cronce]]></category>
  230. <category><![CDATA[DHCP option 121]]></category>
  231. <category><![CDATA[DHCP starvation attack]]></category>
  232. <category><![CDATA[Dynamic Host Control Protocol]]></category>
  233. <category><![CDATA[John Kristoff]]></category>
  234. <category><![CDATA[Leviathan Security]]></category>
  235. <category><![CDATA[Lizzie Moratti]]></category>
  236. <category><![CDATA[Packet Clearing House]]></category>
  237. <guid isPermaLink="false">https://krebsonsecurity.com/?p=67184</guid>
  238.  
  239. <description><![CDATA[Virtual private networking (VPN) companies market their services as a way to prevent anyone from snooping on your Internet usage. But new research suggests this is a dangerous assumption when connecting to a VPN via an untrusted network, because attackers on the same network could force a target's traffic off of the protection provided by their VPN without triggering any alerts to the user.]]></description>
  240. <content:encoded><![CDATA[<p>Virtual private networking (VPN) companies market their services as a way to prevent anyone from snooping on your Internet usage. But new research suggests this is a dangerous assumption when connecting to a VPN via an untrusted network, because attackers on the same network could force a target&#8217;s traffic off of the protection provided by their VPN without triggering any alerts to the user.</p>
  241. <div id="attachment_67354" style="width: 760px" class="wp-caption aligncenter"><img aria-describedby="caption-attachment-67354" decoding="async" loading="lazy" class=" wp-image-67354" src="https://krebsonsecurity.com/wp-content/uploads/2024/05/tunnelvision.png" alt="" width="750" height="569" /><p id="caption-attachment-67354" class="wp-caption-text">Image: Shutterstock.</p></div>
  242. <p>When a device initially tries to connect to a network, it broadcasts a message to the entire local network stating that it is requesting an Internet address. Normally, the only system on the network that notices this request and replies is the router responsible for managing the network to which the user is trying to connect.</p>
  243. <p>The machine on a network responsible for fielding these requests is called a <strong>Dynamic Host Configuration Protocol</strong> (DHCP) server, which will issue time-based leases for IP addresses. The DHCP server also takes care of setting a specific local address &#8212; known as an <strong>Internet gateway</strong> &#8212; that all connecting systems will use as a primary route to the Web.</p>
  244. <p>VPNs work by creating a virtual network interface that serves as an encrypted tunnel for communications. But researchers at <strong>Leviathan Security</strong> say they&#8217;ve discovered it&#8217;s possible to abuse an obscure feature built into the DHCP standard so that other users on the local network are forced to connect to a rogue DHCP server.</p>
  245. <p>&#8220;Our technique is to run a DHCP server on the same network as a targeted VPN user and to also set our DHCP configuration to use itself as a gateway,&#8221; Leviathan researchers <strong>Lizzie Moratti</strong> and <strong>Dani Cronce</strong> wrote. &#8220;When the traffic hits our gateway, we use traffic forwarding rules on the DHCP server to pass traffic through to a legitimate gateway while we snoop on it.&#8221;</p>
  246. <p>The feature being abused here is known as <a href="https://datatracker.ietf.org/doc/html/rfc3442" target="_blank" rel="noopener">DHCP option 121</a>, and it allows a DHCP server to set a route on the VPN user&#8217;s system that is more specific than those used by most VPNs. Abusing this option, Leviathan found, effectively gives an attacker on the local network the ability to set up routing rules that have a higher priority than the routes for the virtual network interface that the target&#8217;s VPN creates.</p>
  247. <p>&#8220;Pushing a route also means that the network traffic will be sent over the same interface as the DHCP server instead of the virtual network interface,&#8221; the Leviathan researchers said. &#8220;This is intended functionality that isn’t clearly stated in the RFC [standard]. Therefore, for the routes we push, it is never encrypted by the VPN’s virtual interface but instead transmitted by the network interface that is talking to the DHCP server. As an attacker, we can select which IP addresses go over the tunnel and which addresses go over the network interface talking to our DHCP server.&#8221;</p>
  248. <p>Leviathan found they could force VPNs on the local network that already had a connection to arbitrarily request a new one. In this well-documented tactic, known as a <a href="https://www.prosec-networks.com/en/blog/dhcp-starvation-attack/" target="_blank" rel="noopener">DHCP starvation attack</a>, an attacker floods the DHCP server with requests that consume all available IP addresses that can be allocated. Once the network&#8217;s legitimate DHCP server is completely tied up, the attacker can then have their rogue DHCP server respond to all pending requests.</p>
  249. <div style="text-align: center;"><iframe loading="lazy" title="YouTube video player" src="https://www.youtube.com/embed/ajsLmZia6UU?si=OYDck1VdGoLF0XFU" width="750" height="415" frameborder="0" allowfullscreen="allowfullscreen"></iframe></div>
  250. <p>&#8220;This technique can also be used against an already established VPN connection once the VPN user’s host needs to renew a lease from our DHCP server,&#8221; the researchers wrote. &#8220;We can artificially create that scenario by setting a short lease time in the DHCP lease, so the user updates their routing table more frequently. In addition, the VPN control channel is still intact because it already uses the physical interface for its communication. In our testing, the VPN always continued to report as connected, and the kill switch was never engaged to drop our VPN connection.&#8221;</p>
  251. <p>The researchers say their methods could be used by an attacker who compromises a DHCP server or wireless access point, or by a rogue network administrator who owns the infrastructure themselves and maliciously configures it. Alternatively, an attacker could set up an &#8220;<a href="https://www.techtarget.com/searchsecurity/definition/evil-twin" target="_blank" rel="noopener">evil twin</a>&#8221; wireless hotspot that mimics the signal broadcast by a legitimate provider.</p>
  252. <p><H2>ANALYSIS</H2></p>
  253. <p><strong>Bill Woodcock</strong> is executive director at <a href="http://www.pch.net" target="_blank" rel="noopener">Packet Clearing House</a>, a nonprofit based in San Francisco. Woodcock said Option 121 has been included in the DHCP standard since 2002, which means the attack described by Leviathan has technically been possible for the last 22 years.</p>
  254. <p>&#8220;They&#8217;re realizing now that this can be used to circumvent a VPN in a way that&#8217;s really problematic, and they&#8217;re right,&#8221; Woodcock said.</p>
  255. <p>Woodcock said anyone who might be a target of spear phishing attacks should be very concerned about using VPNs on an untrusted network.</p>
  256. <p>&#8220;Anyone who is in a position of authority or maybe even someone who is just a high net worth individual, those are all very reasonable targets of this attack,&#8221; he said. &#8220;If I were trying to do an attack against someone at a relatively high security company and I knew where they typically get their coffee or sandwich at twice a week, this is a very effective tool in that toolbox. I&#8217;d be a little surprised if it wasn&#8217;t already being exploited in that way, because again this isn&#8217;t rocket science. It&#8217;s just thinking a little outside the box.&#8221;<span id="more-67184"></span></p>
  257. <p>Successfully executing this attack on a network likely would not allow an attacker to see all of a target&#8217;s traffic or browsing activity. That&#8217;s because for the vast majority of the websites visited by the target, the content is encrypted (the site&#8217;s address begins with https://). However, an attacker would still be able to see the metadata &#8212; such as the source and destination addresses &#8212; of any traffic flowing by.</p>
  258. <p>KrebsOnSecurity shared Leviathan&#8217;s research with <a href="https://www.netscout.com/asert/john-kristoff" target="_blank" rel="noopener">John Kristoff</a>, founder of <a href="https://dataplane.org/" rel="noopener" target="_blank">dataplane.org</a> and a PhD candidate in computer science at the <strong>University of Illinois Chicago</strong>. Kristoff said practically all user-edge network gear, including WiFi deployments, support some form of rogue DHCP server detection and mitigation, but that it&#8217;s unclear how widely deployed those protections are in real-world environments.</p>
  259. <p>&#8220;However, and I think this is a key point to emphasize, an untrusted network is an untrusted network, which is why you&#8217;re usually employing the VPN in the first place,&#8221; Kristoff said. &#8220;If [the] local network is inherently hostile and has no qualms about operating a rogue DHCP server, then this is a sneaky technique that could be used to de-cloak some traffic &#8211; and if done carefully, I&#8217;m sure a user might never notice.&#8221;</p>
  260. <h2>MITIGATIONS</h2>
  261. <p>According to Leviathan, there are several ways to minimize the threat from rogue DHCP servers on an unsecured network. One is using a device powered by the <strong>Android</strong> operating system, which apparently ignores DHCP option 121.</p>
  262. <p>Relying on a temporary wireless hotspot controlled by a cellular device you own also effectively blocks this attack.</p>
  263. <p>&#8220;They create a password-locked LAN with automatic network address translation,&#8221; the researchers wrote of cellular hot-spots. &#8220;Because this network is completely controlled by the cellular device and requires a password, an attacker should not have local network access.&#8221;</p>
  264. <p>Leviathan&#8217;s Moratti said another mitigation is to run your VPN from inside of a virtual machine (VM) &#8212; like Parallels, VMware or VirtualBox. VPNs run inside of a VM are not vulnerable to this attack, Moratti said, provided they are not run in &#8220;<a href="https://www.virtualbox.org/manual/ch06.html#network_bridged" rel="noopener" target="_blank">bridged mode</a>,&#8221; which causes the VM to replicate another node on the network.</p>
  265. <p>In addition, a technology called &#8220;deep packet inspection&#8221; can be used to deny all in- and outbound traffic from the physical interface except for the DHCP and the VPN server. However, Leviathan says this approach opens up a potential &#8220;side channel&#8221; attack that could be used to determine the destination of traffic.</p>
  266. <p>&#8220;This could be theoretically done by performing traffic analysis on the volume a target user sends when the attacker&#8217;s routes are installed compared to the baseline,&#8221; they wrote. &#8220;In addition, this selective denial-of-service is unique as it could be used to censor specific resources that an attacker doesn&#8217;t want a target user to connect to even while they are using the VPN.&#8221;</p>
  267. <p>Moratti said Leviathan&#8217;s research shows that many VPN providers are currently making promises to their customers that their technology can&#8217;t keep.</p>
  268. <p>&#8220;VPNs weren&#8217;t designed to keep you more secure on your local network, but to keep your traffic more secure on the Internet,&#8221; Moratti said. &#8220;When you start making assurances that your product protects people from seeing your traffic, there&#8217;s an assurance or promise that can&#8217;t be met.&#8221;</p>
  269. <p>A copy of Leviathan&#8217;s research, along with code intended to allow others to duplicate their findings in a lab environment, is available <a href="https://www.leviathansecurity.com/blog/tunnelvision" target="_blank" rel="noopener">here</a>.</p>
  270. ]]></content:encoded>
  271. <wfw:commentRss>https://krebsonsecurity.com/2024/05/why-your-vpn-may-not-be-as-secure-as-it-claims/feed/</wfw:commentRss>
  272. <slash:comments>37</slash:comments>
  273. </item>
  274. <item>
  275. <title>Man Who Mass-Extorted Psychotherapy Patients Gets Six Years</title>
  276. <link>https://krebsonsecurity.com/2024/04/man-who-mass-extorted-psychotherapy-patients-gets-six-years/</link>
  277. <comments>https://krebsonsecurity.com/2024/04/man-who-mass-extorted-psychotherapy-patients-gets-six-years/#comments</comments>
  278. <dc:creator><![CDATA[BrianKrebs]]></dc:creator>
  279. <pubDate>Tue, 30 Apr 2024 13:34:32 +0000</pubDate>
  280. <category><![CDATA[Ne'er-Do-Well News]]></category>
  281. <category><![CDATA[Antti Kurittu]]></category>
  282. <category><![CDATA[ColdFusion botnet]]></category>
  283. <category><![CDATA[hack the planet]]></category>
  284. <category><![CDATA[julius zeekill kivimaki]]></category>
  285. <category><![CDATA[Lizard Squad]]></category>
  286. <category><![CDATA[ransom_man]]></category>
  287. <category><![CDATA[Vastaamo Psychotherapy Center]]></category>
  288. <category><![CDATA[Ville Tapio]]></category>
  289. <guid isPermaLink="false">https://krebsonsecurity.com/?p=67317</guid>
  290.  
  291. <description><![CDATA[A 26-year-old Finnish man was sentenced to more than six years in prison today after being convicted of hacking into an online psychotherapy clinic, leaking tens of thousands of patient therapy records, and attempting to extort the clinic and patients.]]></description>
  292. <content:encoded><![CDATA[<p>A 26-year-old Finnish man was sentenced to more than six years in prison today after being convicted of hacking into an online psychotherapy clinic, leaking tens of thousands of patient therapy records, and attempting to extort the clinic and patients.</p>
  293. <p><img decoding="async" loading="lazy" class="aligncenter  wp-image-61773" src="https://krebsonsecurity.com/wp-content/uploads/2022/11/kikmaki-wanted.png" alt="" width="750" height="357" srcset="https://krebsonsecurity.com/wp-content/uploads/2022/11/kikmaki-wanted.png 2936w, https://krebsonsecurity.com/wp-content/uploads/2022/11/kikmaki-wanted-768x366.png 768w, https://krebsonsecurity.com/wp-content/uploads/2022/11/kikmaki-wanted-1536x731.png 1536w, https://krebsonsecurity.com/wp-content/uploads/2022/11/kikmaki-wanted-2048x975.png 2048w, https://krebsonsecurity.com/wp-content/uploads/2022/11/kikmaki-wanted-782x372.png 782w" sizes="(max-width: 750px) 100vw, 750px" /></p>
  294. <p>On October 21, 2020, the <strong>Vastaamo Psychotherapy Center</strong> in Finland became the target of blackmail when a tormentor identified as “ransom_man” demanded payment of 40 bitcoins (~450,000 euros at the time) in return for a promise not to publish highly sensitive therapy session notes Vastaamo had exposed online.</p>
  295. <p>Ransom_man announced on the dark web that he would start publishing 100 patient profiles every 24 hours. When Vastaamo declined to pay, ransom_man shifted to extorting individual patients. According to Finnish police, some 22,000 victims reported extortion attempts targeting them personally, targeted emails that threatened to publish their therapy notes online unless paid a 500 euro ransom.</p>
  296. <p>Finnish prosecutors quickly zeroed in on a suspect:<strong> Julius &#8220;Zeekill&#8221; Kivimäki</strong>, a notorious criminal hacker convicted of committing tens of thousands of cybercrimes before he became an adult. After being charged with the attack in October 2022, Kivimäki fled the country. He was <a href="https://krebsonsecurity.com/2023/02/finlands-most-wanted-hacker-nabbed-in-france/" target="_blank" rel="noopener">arrested four months later in France</a>, hiding out under an assumed name and passport.</p>
  297. <p><strong>Antti Kurittu</strong> is a former criminal investigator who worked on an investigation involving Kivimäki’s use of the Zbot botnet, among other activities Kivimäki engaged in as a member of the hacker group <a href="https://krebsonsecurity.com/2015/02/webnic-registrar-blamed-for-hijack-of-lenovo-google-domains/" target="_blank" rel="noopener">Hack the Planet</a> (HTP).</p>
  298. <p>Kurittu said the prosecution had demanded at least seven years in jail, and that the sentence handed down was six years and three months. Kurittu said prosecutors knocked a few months off of Kivimäki&#8217;s sentence because he agreed to pay compensation to his victims, and that Kivimäki will remain in prison during any appeal process.</p>
  299. <p>&#8220;I think the sentencing was as expected, knowing the Finnish judicial system,&#8221; Kurittu told KrebsOnSecurity. &#8220;As Kivimäki has not been sentenced to a non-suspended prison sentence during the last five years, he will be treated as a first-timer, his previous convictions notwithstanding.&#8221;</p>
  300. <p>But because juvenile convictions in Finland don&#8217;t count towards determining whether somebody is a first-time offender, Kivimäki will end up serving approximately half of his sentence.</p>
  301. <p>&#8220;This seems like a short sentence when taking into account the gravity of his actions and the life-altering consequences to thousands of people, but it&#8217;s almost the maximum the law allows for,&#8221; Kurittu said.<span id="more-67317"></span></p>
  302. <p>Kivimäki initially gained notoriety as a self-professed member of the <a href="https://krebsonsecurity.com/tag/lizard-squad/" target="_blank" rel="noopener">Lizard Squad</a>, a mainly low-skilled hacker group that specialized in DDoS attacks. But American and Finnish investigators say Kivimäki’s involvement in cybercrime dates back to at least 2008, when he was introduced to a founding member of what would soon become HTP.</p>
  303. <p>Finnish police said Kivimäki also used the nicknames “Ryan”, “RyanC” and “Ryan Cleary” (Ryan Cleary was actually a member of a rival hacker group — <a href="https://en.wikipedia.org/wiki/LulzSec" target="_blank" rel="noopener">LulzSec</a> — who was sentenced to prison for hacking).</p>
  304. <p>Kivimäki and other HTP members were involved in mass-compromising web servers using known vulnerabilities, and by 2012 Kivimäki’s alias Ryan Cleary was selling access to those servers in the form of a DDoS-for-hire service. Kivimäki was 15 years old at the time.</p>
  305. <p>In 2013, investigators going through devices seized from Kivimäki found computer code that had been used to crack more than 60,000 web servers using a previously unknown vulnerability in <strong>Adobe’s ColdFusion</strong> software. KrebsOnSecurity detailed the work of HTP in September 2013, after the group <a href="https://krebsonsecurity.com/2013/09/data-broker-giants-hacked-by-id-theft-service/" target="_blank" rel="noopener">compromised servers inside data brokers LexisNexis, Kroll, and Dun &amp; Bradstreet</a>.</p>
  306. <p>The group used the same ColdFusion flaws <a href="https://krebsonsecurity.com/2013/10/data-broker-hackers-also-compromised-nw3c/" target="_blank" rel="noopener">to break into the National White Collar Crime Center (NWC3)</a>, a non-profit that provides research and investigative support to the <strong>U.S. Federal Bureau of Investigation</strong> (FBI).</p>
  307. <p>As KrebsOnSecurity reported at the time, this small ColdFusion botnet of data broker servers was being controlled by the same cybercriminals who’d <a href="https://krebsonsecurity.com/2013/03/credit-reports-sold-for-cheap-in-the-underweb/" target="_blank" rel="noopener">assumed control over <strong>SSNDOB</strong></a>, which operated one of the underground’s most reliable services for obtaining Social Security Number, dates of birth and credit file information on U.S. residents.</p>
  308. <p>Kivimäki was responsible for making <a href="http://www.forbes.com/sites/insertcoin/2014/08/24/sony-online-entertainment-presidents-flight-diverted-by-psn-hackers-bomb-threat/" target="_blank" rel="noopener">an August 2014 bomb threat</a> against former <strong>Sony Online Entertainment President John Smedley</strong> that grounded an American Airlines plane. Kivimäki also was involved in calling in multiple fake bomb threats and “swatting” incidents — reporting fake hostage situations at an address to prompt a heavily armed police response to that location.</p>
  309. <p><strong>Ville Tapio,</strong> the former CEO of Vastaamo, was fired and also prosecuted following the breach. Ransom_man bragged about Vastaamo&#8217;s sloppy security, noting the company had used the laughably weak username and password &#8220;root/root&#8221; to protect sensitive patient records.</p>
  310. <p>Investigators later found Vastaamo had originally been hacked in 2018 and again in 2019. In April 2023, a Finnish court handed down <a href="https://yle.fi/a/74-20027665" target="_blank" rel="noopener">a three-month sentence for Tapio</a>, but that sentence was suspended because he had no previous criminal record.</p>
  311. ]]></content:encoded>
  312. <wfw:commentRss>https://krebsonsecurity.com/2024/04/man-who-mass-extorted-psychotherapy-patients-gets-six-years/feed/</wfw:commentRss>
  313. <slash:comments>33</slash:comments>
  314. </item>
  315. <item>
  316. <title>FCC Fines Major U.S. Wireless Carriers for Selling Customer Location Data</title>
  317. <link>https://krebsonsecurity.com/2024/04/fcc-fines-major-u-s-wireless-carriers-for-selling-customer-location-data/</link>
  318. <comments>https://krebsonsecurity.com/2024/04/fcc-fines-major-u-s-wireless-carriers-for-selling-customer-location-data/#comments</comments>
  319. <dc:creator><![CDATA[BrianKrebs]]></dc:creator>
  320. <pubDate>Mon, 29 Apr 2024 20:56:42 +0000</pubDate>
  321. <category><![CDATA[Ne'er-Do-Well News]]></category>
  322. <category><![CDATA[AT&T]]></category>
  323. <category><![CDATA[LocationSmart]]></category>
  324. <category><![CDATA[Securus Technologies]]></category>
  325. <category><![CDATA[Sprint]]></category>
  326. <category><![CDATA[T-Mobile]]></category>
  327. <category><![CDATA[U.S. Federal Communications Commission]]></category>
  328. <category><![CDATA[Verizon]]></category>
  329. <guid isPermaLink="false">https://krebsonsecurity.com/?p=67297</guid>
  330.  
  331. <description><![CDATA[The U.S. Federal Communications Commission (FCC) today levied fines totaling nearly $200 million against the four major carriers -- including AT&#038;T, Sprint, T-Mobile and Verizon -- for illegally sharing access to customers' location information without consent.]]></description>
  332. <content:encoded><![CDATA[<p>The <strong>U.S. Federal Communications Commission</strong> (FCC) today levied fines totaling nearly $200 million against the four major carriers &#8212; including <strong>AT&amp;T</strong>, <strong>Sprint</strong>, <strong>T-Mobile</strong> and <strong>Verizon</strong> &#8212; for illegally sharing access to customers&#8217; location information without consent.</p>
  333. <p><img decoding="async" loading="lazy" class="aligncenter wp-image-43845" src="https://krebsonsecurity.com/wp-content/uploads/2018/05/locationtracking.jpg" alt="" width="744" height="482" /></p>
  334. <p>The fines mark the culmination of a more than four-year investigation into the actions of the major carriers. In February 2020, the FCC put all four wireless providers on notice that their practices of sharing access to customer location data were likely violating the law.</p>
  335. <p>The FCC said it found the carriers each sold access to its customers&#8217; location information to &#8216;aggregators,&#8217; who then resold access to the information to third-party location-based service providers.</p>
  336. <p>&#8220;In doing so, each carrier attempted to offload its obligations to obtain customer consent onto downstream recipients of location information, which in many instances meant that no valid customer consent was obtained,&#8221; <a href="https://www.fcc.gov/document/fcc-fines-largest-wireless-carriers-sharing-location-data" target="_blank" rel="noopener">an FCC statement</a> on the action reads. &#8220;This initial failure was compounded when, after becoming aware that their safeguards were ineffective, the carriers continued to sell access to location information without taking reasonable measures to protect it from unauthorized access.&#8221;</p>
  337. <p>The FCC&#8217;s <a href="https://docs.fcc.gov/public/attachments/FCC-24-40A1.pdf" target="_blank" rel="noopener">findings against AT&amp;T</a>, for example, show that AT&amp;T sold customer location data directly or indirectly to at least 88 third-party entities. The FCC <a href="https://docs.fcc.gov/public/attachments/FCC-24-41A1.pdf" target="_blank" rel="noopener">found</a> Verizon sold access to customer location data (indirectly or directly) to 67 third-party entities. Location data for Sprint customers found its way to 86 third-party entities, and to 75 third-parties in the case of T-Mobile customers.</p>
  338. <p>The commission said it took action after <strong>Sen. Ron Wyden</strong> (D-Ore.) <a href="https://www.wyden.senate.gov/imo/media/doc/wyden-securus-location-tracking-letter-to-fcc.pdf" target="_blank" rel="noopener">sent a letter to the FCC</a> detailing how a company called <strong>Securus Technologies</strong> had been selling location data on customers of virtually any major mobile provider to law enforcement officials.</p>
  339. <p>That same month, KrebsOnSecurity <a href="https://krebsonsecurity.com/2018/05/tracking-firm-locationsmart-leaked-location-data-for-customers-of-all-major-u-s-mobile-carriers-in-real-time-via-its-web-site/" target="_blank" rel="noopener">broke the news</a> that <strong>LocationSmart</strong> — a data aggregation firm working with the major wireless carriers — had a free, unsecured demo of its service online that anyone could abuse to find the near-exact location of virtually any mobile phone in North America.<span id="more-67297"></span><span id="more-50646"></span></p>
  340. <p>The carriers <a href="https://krebsonsecurity.com/2018/06/verizon-to-stop-sharing-customer-location-data-with-third-parties/" target="_blank" rel="noopener">promised to &#8220;wind down&#8221; location data sharing agreements</a> with third-party companies. But in 2019, reporting at <a href="https://www.vice.com/en_us/article/nepxbz/i-gave-a-bounty-hunter-300-dollars-located-phone-microbilt-zumigo-tmobile" target="_blank" rel="noopener">Vice.com showed</a> that little had changed, detailing how reporters were able to locate a test phone after paying $300 to a bounty hunter who simply bought the data through a little-known third-party service.</p>
  341. <p>Sen. Wyden said no one who signed up for a cell plan thought they were giving permission for their phone company to sell a detailed record of their movements to anyone with a credit card.</p>
  342. <p>&#8220;I applaud the FCC for following through on my investigation and holding these companies accountable for putting customers’ lives and privacy at risk,” Wyden said in a statement today.</p>
  343. <p>The FCC fined Sprint and T-Mobile $12 million and $80 million respectively. AT&amp;T was fined more than $57 million, while Verizon received a $47 million penalty. Still, these fines represent a tiny fraction of each carrier&#8217;s annual revenues. For example, $47 million is less than one percent of Verizon&#8217;s total wireless service revenue in 2023, which was nearly $77 billion.</p>
  344. <p>The fine amounts vary because they were calculated based in part on the number of days that the carriers continued sharing customer location data after being notified that doing so was illegal (the agency also considered the number of active third-party location data sharing agreements). The FCC notes that AT&amp;T and Verizon each took more than 320 days from the publication of the Times story to wind down their data sharing agreements; T-Mobile took 275 days; Sprint kept sharing customer location data for 386 days.</p>
  345. <p><strong>Update, 6:25 p.m. ET:</strong> Clarified that the FCC launched its investigation at the request of Sen. Wyden.</p>
  346. ]]></content:encoded>
  347. <wfw:commentRss>https://krebsonsecurity.com/2024/04/fcc-fines-major-u-s-wireless-carriers-for-selling-customer-location-data/feed/</wfw:commentRss>
  348. <slash:comments>34</slash:comments>
  349. </item>
  350. <item>
  351. <title>Russian FSB Counterintelligence Chief Gets 9 Years in Cybercrime Bribery Scheme</title>
  352. <link>https://krebsonsecurity.com/2024/04/russian-fsb-counterintelligence-chief-gets-9-years-in-cybercrime-bribery-scheme/</link>
  353. <comments>https://krebsonsecurity.com/2024/04/russian-fsb-counterintelligence-chief-gets-9-years-in-cybercrime-bribery-scheme/#comments</comments>
  354. <dc:creator><![CDATA[BrianKrebs]]></dc:creator>
  355. <pubDate>Mon, 22 Apr 2024 20:07:56 +0000</pubDate>
  356. <category><![CDATA[A Little Sunshine]]></category>
  357. <category><![CDATA[Ne'er-Do-Well News]]></category>
  358. <category><![CDATA[Web Fraud 2.0]]></category>
  359. <category><![CDATA[Alexander Kovalev]]></category>
  360. <category><![CDATA[Artem Zaitsev]]></category>
  361. <category><![CDATA[Federal Security Service (FSB)]]></category>
  362. <category><![CDATA[Ferum Shop]]></category>
  363. <category><![CDATA[Get-Net LLC]]></category>
  364. <category><![CDATA[Grigory Tsaregorodtsev]]></category>
  365. <category><![CDATA[Sky-Fraud]]></category>
  366. <category><![CDATA[Trump's-Dumps]]></category>
  367. <guid isPermaLink="false">https://krebsonsecurity.com/?p=67255</guid>
  368.  
  369. <description><![CDATA[The head of counterintelligence for a division of the Russian Federal Security Service (FSB) was sentenced last week to nine years in a penal colony for accepting a USD $1.7 million bribe to ignore the activities of a prolific Russian cybercrime group that hacked thousands of e-commerce websites. The protection scheme was exposed in 2022 when Russian authorities arrested six members of the group, which sold millions of stolen payment cards at flashy online shops like Trump's Dumps.]]></description>
  370. <content:encoded><![CDATA[<p>The head of counterintelligence for a division of the Russian <strong>Federal Security Service</strong> (FSB) was sentenced last week to nine years in a penal colony for accepting a USD $1.7 million bribe to ignore the activities of a prolific Russian cybercrime group that hacked thousands of e-commerce websites. The protection scheme was exposed in 2022 when Russian authorities arrested six members of the group, which sold millions of stolen payment cards at flashy online shops like <strong>Trump&#8217;s Dumps</strong>.</p>
  371. <div id="attachment_39492" style="width: 760px" class="wp-caption aligncenter"><img aria-describedby="caption-attachment-39492" decoding="async" loading="lazy" class=" wp-image-39492" src="https://krebsonsecurity.com/wp-content/uploads/2017/05/trumpsdumps-580x395.png" alt="" width="750" height="511" srcset="https://krebsonsecurity.com/wp-content/uploads/2017/05/trumpsdumps-580x395.png 580w, https://krebsonsecurity.com/wp-content/uploads/2017/05/trumpsdumps-768x524.png 768w, https://krebsonsecurity.com/wp-content/uploads/2017/05/trumpsdumps-940x641.png 940w, https://krebsonsecurity.com/wp-content/uploads/2017/05/trumpsdumps.png 1295w" sizes="(max-width: 750px) 100vw, 750px" /><p id="caption-attachment-39492" class="wp-caption-text">A now-defunct carding shop that sold stolen credit cards and invoked 45&#8217;s likeness and name.</p></div>
  372. <p>As <a href="https://therecord.media/former-fsb-officer-sentenced-russia-helping-hackers" target="_blank" rel="noopener">reported</a> by <em>The Record</em>, a Russian court last week sentenced former FSB officer <strong>Grigory Tsaregorodtsev</strong> for taking a $1.7 million bribe from a cybercriminal group that was seeking a &#8220;roof,&#8221; a well-placed, corrupt law enforcement official who could be counted on to both disregard their illegal hacking activities and run interference with authorities in the event of their arrest.</p>
  373. <p>Tsaregorodtsev was head of the counterintelligence department for a division of the FSB based in Perm, Russia. In February 2022, Russian <a href="https://krebsonsecurity.com/2022/02/russian-govt-continues-carding-shop-crackdown/" target="_blank" rel="noopener">authorities arrested six men in the Perm region</a> accused of selling stolen payment card data. They also seized multiple carding shops run by the gang, including <strong>Ferum Shop</strong>, <strong>Sky-Fraud</strong>, and <strong>Trump&#8217;s Dumps</strong>, a popular fraud store that invoked the 45th president’s likeness and promised to &#8220;make credit card fraud great again.&#8221;</p>
  374. <p>All of the domains seized in that raid were registered by an IT consulting company in Perm called <strong>Get-net LLC</strong>, which was owned in part by <strong>Artem Zaitsev</strong> &#8212; one of the six men arrested. Zaitsev reportedly was a well-known programmer whose company supplied services and leasing to the local FSB field office.<span id="more-67255"></span></p>
  375. <div id="attachment_58442" style="width: 759px" class="wp-caption aligncenter"><img aria-describedby="caption-attachment-58442" decoding="async" loading="lazy" class=" wp-image-58442" src="https://krebsonsecurity.com/wp-content/uploads/2022/02/deptk-td.png" alt="" width="749" height="483" /><p id="caption-attachment-58442" class="wp-caption-text">The message for Trump&#8217;s Dumps users left behind by Russian authorities that seized the domain in 2022.</p></div>
  376. <p>Russian news sites report that Internal Affairs officials with the FSB grew suspicious when Tsaregorodtsev became a little too interested in the case following the hacking group&#8217;s arrests. The former FSB agent had reportedly assured the hackers he could have their case transferred and that they would soon be free.</p>
  377. <p>But when that promised freedom didn&#8217;t materialize, four the of the defendants pulled the walls down on the scheme and brought down their own roof. The FSB arrested Tsaregorodtsev, and seized $154,000 in cash, 100 gold bars, real estate and expensive cars.</p>
  378. <p>At Tsaregorodtsev&#8217;s trial, his lawyers argued that their client wasn&#8217;t guilty of bribery per se, but that he did admit to fraud because he was ultimately unable to fully perform the services for which he&#8217;d been hired.</p>
  379. <p>The Russian news outlet <em>Kommersant</em> reports that all four of those who cooperated were released with probation or correctional labor. Zaitsev received a sentence of 3.5 years in prison, and defendant <strong>Alexander Kovalev</strong> got four years.</p>
  380. <p>In 2017, KrebsOnSecurity <a href="https://krebsonsecurity.com/2017/05/trumps-dumps-making-dumps-great-again/" target="_blank" rel="noopener">profiled Trump&#8217;s Dumps</a>, and found the contact address listed on the site was tied to an email address used to register more than a dozen domains that were made to look like legitimate Javascript calls many e-commerce sites routinely make to process transactions &#8212; such as &#8220;js-link[dot]su,&#8221; &#8220;js-stat[dot]su,&#8221; and &#8220;js-mod[dot]su.&#8221;</p>
  381. <p>Searching on those malicious domains revealed <a href="https://web.archive.org/web/20161114152809/https://www.riskiq.com/blog/labs/magecart-keylogger-injection/" target="_blank" rel="noopener">a 2016 report from RiskIQ</a>, which shows the domains featured prominently in a series of hacking campaigns against e-commerce websites. According to RiskIQ, the attacks targeted online stores running outdated and unpatched versions of shopping cart software from <strong>Magento</strong>, <strong>Powerfront</strong> and <strong>OpenCart</strong>.</p>
  382. <p>Those shopping cart flaws allowed the crooks to install &#8220;web skimmers,&#8221; malicious Javascript used to steal credit card details and other information from payment forms on the checkout pages of vulnerable e-commerce sites. The stolen customer payment card details were then sold on sites like Trump&#8217;s Dumps and Sky-Fraud.</p>
  383. ]]></content:encoded>
  384. <wfw:commentRss>https://krebsonsecurity.com/2024/04/russian-fsb-counterintelligence-chief-gets-9-years-in-cybercrime-bribery-scheme/feed/</wfw:commentRss>
  385. <slash:comments>15</slash:comments>
  386. </item>
  387. <item>
  388. <title>Who Stole 3.6M Tax Records from South Carolina?</title>
  389. <link>https://krebsonsecurity.com/2024/04/who-stole-3-6m-tax-records-from-south-carolina/</link>
  390. <comments>https://krebsonsecurity.com/2024/04/who-stole-3-6m-tax-records-from-south-carolina/#comments</comments>
  391. <dc:creator><![CDATA[BrianKrebs]]></dc:creator>
  392. <pubDate>Tue, 16 Apr 2024 11:26:55 +0000</pubDate>
  393. <category><![CDATA[Breadcrumbs]]></category>
  394. <category><![CDATA[Data Breaches]]></category>
  395. <category><![CDATA[Ne'er-Do-Well News]]></category>
  396. <category><![CDATA[Tax Refund Fraud]]></category>
  397. <category><![CDATA[Aleksandr Ermakov]]></category>
  398. <category><![CDATA[Associated Press]]></category>
  399. <category><![CDATA[Embargo]]></category>
  400. <category><![CDATA[Home Depot breach]]></category>
  401. <category><![CDATA[Jeffrey Collins]]></category>
  402. <category><![CDATA[Mark Keel]]></category>
  403. <category><![CDATA[Mazafaka]]></category>
  404. <category><![CDATA[Mikhail Shefel]]></category>
  405. <category><![CDATA[Nikki Haley]]></category>
  406. <category><![CDATA[rescator]]></category>
  407. <category><![CDATA[Shtazi]]></category>
  408. <category><![CDATA[target breach]]></category>
  409. <category><![CDATA[tax refund fraud]]></category>
  410. <category><![CDATA[tax return fraud]]></category>
  411. <category><![CDATA[The Post and Courier]]></category>
  412. <category><![CDATA[U.S. Internal Revenue Service]]></category>
  413. <category><![CDATA[Verified]]></category>
  414. <guid isPermaLink="false">https://krebsonsecurity.com/?p=67190</guid>
  415.  
  416. <description><![CDATA[For nearly a dozen years, residents of South Carolina have been kept in the dark by state and federal investigators over who was responsible for hacking into the state's revenue department in 2012 and stealing tax and bank account information for 3.6 million people. The answer may no longer be a mystery: KrebsOnSecurity found compelling clues suggesting the intrusion was carried out by the same Russian hacking crew that stole of millions of payment card records from big box retailers like Home Depot and Target in the years that followed.]]></description>
  417. <content:encoded><![CDATA[<p><img decoding="async" loading="lazy" class="aligncenter wp-image-42398" src="https://krebsonsecurity.com/wp-content/uploads/2018/01/taxthiefa.png" alt="" width="750" height="275" /></p>
  418. <p>For nearly a dozen years, residents of South Carolina have been kept in the dark by state and federal investigators over who was responsible for hacking into the state&#8217;s revenue department in 2012 and stealing tax and bank account information for 3.6 million people. The answer may no longer be a mystery: KrebsOnSecurity found compelling clues suggesting the intrusion was carried out by the same Russian hacking crew that stole of millions of payment card records from big box retailers like <strong>Home Depot</strong> and <strong>Target</strong> in the years that followed.</p>
  419. <p>Questions about who stole tax and financial data on roughly three quarters of all South Carolina residents came to the fore last week at the confirmation hearing of <strong>Mark Keel</strong>, who was appointed in 2011 by <strong>Gov. Nikki Haley</strong> to head the state&#8217;s law enforcement division. If approved, this would be Keel&#8217;s third six-year term in that role.</p>
  420. <p><em>The Associated Press</em> <a href="https://apnews.com/article/south-carolina-hacking-tax-returns-2012-5984ce1c6f47938da7a671d0fccadd22" target="_blank" rel="noopener">reports</a> that Keel was careful not to release many details about the breach at his hearing, telling lawmakers he knows who did it but that he wasn&#8217;t ready to name anyone.</p>
  421. <p>&#8220;I think the fact that we didn&#8217;t come up with a whole lot of people&#8217;s information that got breached is a testament to the work that people have done on this case,&#8221; Keel asserted.</p>
  422. <p>A ten-year <a href="//www.postandcourier.com/columbia/news/scs-massive-data-breach-10-years-later-questions-linger-as-investigation-remains-open/article_29dd8164-4025-11ed-9433-73cafd23fadb.html" target="_blank" rel="noopener">retrospective</a> published in 2022 by <em>The Post and Courier</em> in Columbia, S.C. said investigators determined the breach began on Aug. 13, 2012, after a state IT contractor clicked a malicious link in an email. State officials said they found out about the hack from federal law enforcement on October 10, 2012.</p>
  423. <p>KrebsOnSecurity examined posts across dozens of cybercrime forums around that time, and found only one instance of someone selling large volumes of tax data in the year surrounding the breach date.</p>
  424. <p>On Oct. 7, 2012 &#8212; three days before South Carolina officials say they first learned of the intrusion &#8212; a notorious cybercriminal who goes by the handle &#8220;<strong>Rescator</strong>&#8221; advertised the sale of &#8220;a database of the tax department of one of the states.&#8221;</p>
  425. <p>&#8220;Bank account information, SSN and all other information,&#8221; Rescator&#8217;s sales thread on the Russian-language crime forum <strong>Embargo</strong> read. &#8220;If you purchase the entire database, I will give you access to it.&#8221;</p>
  426. <p>A week later, Rescator posted a similar offer on the exclusive Russian forum <strong>Mazafaka</strong>, saying he was selling information from a U.S. state tax database, without naming the state. Rescator said the data exposed included Social Security Number (SSN), employer, name, address, phone, taxable income, tax refund amount, and bank account number.</p>
  427. <p>&#8220;There is a lot of information, I am ready to sell the entire database, with access to the database, and in parts,&#8221; Rescator told Mazafaka members. &#8220;There is also information on corporate taxpayers.&#8221;<span id="more-67190"></span></p>
  428. <p>On Oct. 26, 2012, the state announced the breach publicly. State officials said they were working with investigators from the <strong>U.S. Secret Service</strong> and digital forensics experts from Mandiant, which produced <a href="https://oag.ca.gov/system/files/Mandiant%20Report_0.pdf" target="_blank" rel="noopener">an incident report</a> (PDF) that was later published by South Carolina Dept. of Revenue. KrebsOnSecurity sought comment from the Secret Service, South Carolina prosecutors, and Mr. Keel&#8217;s office. This story will be updated if any of them respond. <strong>Update:</strong> The Secret Service declined to comment.</p>
  429. <p>On Nov. 18, 2012, Rescator told fellow denizens of the forum <strong>Verified</strong> he was selling a database of 65,000 records with bank account information from several smaller, regional financial institutions. Rescator&#8217;s sales thread on Verified listed more than a dozen database fields, including account number, name, address, phone, tax ID, date of birth, employer and occupation.</p>
  430. <p>Asked to provide more context about the database for sale, Rescator told forum members the database included financial records related to tax filings of a U.S. state. Rescator added that there was a second database of around 80,000 corporations that included social security numbers, names and addresses, but no financial information.</p>
  431. <p>The AP says South Carolina paid $12 million to Experian for identity theft protection and credit monitoring for its residents after the breach.</p>
  432. <p>&#8220;At the time, it was one of the largest breaches in U.S. history but has since been surpassed greatly by hacks to Equifax, Yahoo, Home Depot, Target and PlayStation,&#8221; the AP&#8217;s <strong>Jeffrey Collins</strong> wrote.</p>
  433. <p>As it happens, Rescator&#8217;s criminal hacking crew was directly responsible for <a href="https://krebsonsecurity.com/tag/target-breach/" target="_blank" rel="noopener">the 2013 breach at Target</a> and the 2014 <a href="https://krebsonsecurity.com/tag/home-depot-breach/" target="_blank" rel="noopener">hack of Home Depot</a>. The Target intrusion saw Rescator&#8217;s cybercrime shops selling roughly 40 million stolen payment cards, and 56 million cards from Home Depot customers.</p>
  434. <p>Who is Rescator? On Dec. 14, 2023, KrebsOnSecurity published the results of <a href="https://krebsonsecurity.com/2023/12/ten-years-later-new-clues-in-the-target-breach/" target="_blank" rel="noopener">a 10-year investigation into the identity of Rescator</a>, a.k.a. <strong>Mikhail Borisovich Shefel</strong>, a 36-year-old who lives in Moscow and who recently changed his last name to Lenin.</p>
  435. <p><img decoding="async" loading="lazy" class="aligncenter wp-image-67207" src="https://krebsonsecurity.com/wp-content/uploads/2024/04/shefel-fb1.png" alt="" width="750" height="572" srcset="https://krebsonsecurity.com/wp-content/uploads/2024/04/shefel-fb1.png 942w, https://krebsonsecurity.com/wp-content/uploads/2024/04/shefel-fb1-768x585.png 768w, https://krebsonsecurity.com/wp-content/uploads/2024/04/shefel-fb1-782x596.png 782w" sizes="(max-width: 750px) 100vw, 750px" /></p>
  436. <p>Mr. Keel&#8217;s assertion that somehow the efforts of South Carolina officials following the breach may have lessened its impact on citizens seems unlikely. The stolen tax and financial data appears to have been sold openly on cybercrime forums by one of the Russian underground&#8217;s most aggressive and successful hacking crews.</p>
  437. <p>While there are no indications from reviewing forum posts that Rescator ever sold the data, his sales threads came at a time when the incidence of <a href="https://krebsonsecurity.com/category/tax-refund-fraud/" target="_blank" rel="noopener">tax refund fraud</a> was skyrocketing.</p>
  438. <p>Tax-related identity theft occurs when someone uses a stolen identity and SSN to file a tax return in that person&#8217;s name claiming a fraudulent refund. Victims usually first learn of the crime after having their returns rejected because scammers beat them to it. Even those who are not required to file a return can be victims of refund fraud, <em>as can those who are not actually owed a refund</em> from the <strong>U.S. Internal Revenue Service</strong> (IRS).</p>
  439. <p>According to <a title="http://www.cbsnews.com/news/irs-refunded-4-billion-to-identity-thieves-last-year-inspector-generals-report-says/" href="http://www.cbsnews.com/news/irs-refunded-4-billion-to-identity-thieves-last-year-inspector-generals-report-says/" target="_blank" rel="noopener">a 2013 report</a> from the Treasury Inspector General’s office, the IRS issued nearly $4 billion in bogus tax refunds in 2012, and more than $5.8 billion in 2013. The money largely was sent to people who stole SSNs and other information on U.S. citizens, and then filed fraudulent tax returns on those individuals claiming a large refund but at a different address.</p>
  440. <p>It remains unclear why Shefel has never been officially implicated in the breaches at Target, Home Depot, or in South Carolina. It may be that Shefel <em>has</em> been indicted, and that those indictments remain sealed for some reason. Perhaps prosecutors were hoping Shefel would decide to leave Russia, at which point it would be easier to apprehend him if he believed no one was looking for him.</p>
  441. <p>But all signs are that Shefel is deeply rooted in Russia, and has no plans to leave. In January 2024, authorities in Australia, the United States and the U.K. levied financial sanctions against 33-year-old Russian man <strong>Aleksandr Ermakov</strong> for allegedly stealing data on 10 million customers of the Australian health insurance giant Medibank.</p>
  442. <p>A week after those sanctions were put in place, KrebsOnSecurity published <a href="https://krebsonsecurity.com/2024/01/who-is-alleged-medibank-hacker-aleksandr-ermakov/" target="_blank" rel="noopener">a deep dive on Ermakov</a>, which found that he co-ran a Moscow-based IT security consulting business along with Mikhail Shefel called<strong> Shtazi-IT</strong>.</p>
  443. <div id="attachment_66196" style="width: 759px" class="wp-caption aligncenter"><img aria-describedby="caption-attachment-66196" decoding="async" loading="lazy" class=" wp-image-66196" src="https://krebsonsecurity.com/wp-content/uploads/2024/01/shtazi-ru.png" alt="" width="749" height="307" srcset="https://krebsonsecurity.com/wp-content/uploads/2024/01/shtazi-ru.png 1806w, https://krebsonsecurity.com/wp-content/uploads/2024/01/shtazi-ru-768x315.png 768w, https://krebsonsecurity.com/wp-content/uploads/2024/01/shtazi-ru-1536x629.png 1536w, https://krebsonsecurity.com/wp-content/uploads/2024/01/shtazi-ru-782x320.png 782w" sizes="(max-width: 749px) 100vw, 749px" /><p id="caption-attachment-66196" class="wp-caption-text">A Google-translated version of Shtazi dot ru. Image: Archive.org.</p></div>
  444. ]]></content:encoded>
  445. <wfw:commentRss>https://krebsonsecurity.com/2024/04/who-stole-3-6m-tax-records-from-south-carolina/feed/</wfw:commentRss>
  446. <slash:comments>15</slash:comments>
  447. </item>
  448. <item>
  449. <title>Crickets from Chirp Systems in Smart Lock Key Leak</title>
  450. <link>https://krebsonsecurity.com/2024/04/crickets-from-chirp-systems-in-smart-lock-key-leak/</link>
  451. <comments>https://krebsonsecurity.com/2024/04/crickets-from-chirp-systems-in-smart-lock-key-leak/#comments</comments>
  452. <dc:creator><![CDATA[BrianKrebs]]></dc:creator>
  453. <pubDate>Mon, 15 Apr 2024 14:51:17 +0000</pubDate>
  454. <category><![CDATA[A Little Sunshine]]></category>
  455. <category><![CDATA[Latest Warnings]]></category>
  456. <category><![CDATA[Security Tools]]></category>
  457. <category><![CDATA[August.com]]></category>
  458. <category><![CDATA[Chirp Systems]]></category>
  459. <category><![CDATA[Matt Brown]]></category>
  460. <category><![CDATA[ProPublica]]></category>
  461. <category><![CDATA[RealPage Inc.]]></category>
  462. <category><![CDATA[U.S. Cybersecurity & Infrastructure Security Agency]]></category>
  463. <guid isPermaLink="false">https://krebsonsecurity.com/?p=67102</guid>
  464.  
  465. <description><![CDATA[The U.S. government is warning that smart locks securing entry to an estimated 50,000 dwellings nationwide contain hard-coded credentials that can be used to remotely open any of the locks. The lock's maker Chirp Systems remains unresponsive, even though it was first notified about the critical weakness in March 2021. Meanwhile, Chirp's parent company, RealPage, Inc., is being sued by multiple U.S. states for allegedly colluding with landlords to illegally raise rents.]]></description>
  466. <content:encoded><![CDATA[<p>The U.S. government is warning that &#8220;smart locks&#8221; securing entry to an estimated 50,000 dwellings nationwide contain hard-coded credentials that can be used to remotely open any of the locks. The lock&#8217;s maker <strong>Chirp Systems</strong> remains unresponsive, even though it was first notified about the critical weakness in March 2021. Meanwhile, Chirp&#8217;s parent company, <strong>RealPage, Inc.</strong>, is being sued by multiple U.S. states for allegedly colluding with landlords to illegally raise rents.</p>
  467. <p><img decoding="async" loading="lazy" class="aligncenter wp-image-67129" src="https://krebsonsecurity.com/wp-content/uploads/2024/04/chirpsystems.png" alt="" width="751" height="451" srcset="https://krebsonsecurity.com/wp-content/uploads/2024/04/chirpsystems.png 1309w, https://krebsonsecurity.com/wp-content/uploads/2024/04/chirpsystems-768x462.png 768w, https://krebsonsecurity.com/wp-content/uploads/2024/04/chirpsystems-782x470.png 782w" sizes="(max-width: 751px) 100vw, 751px" /></p>
  468. <p>On March 7, 2024, the <strong>U.S. Cybersecurity &amp; Infrastructure Security Agency</strong> (CISA) <a href="https://www.cisa.gov/news-events/ics-advisories/icsa-24-067-01" target="_blank" rel="noopener">warned</a> about a remotely exploitable vulnerability with &#8220;low attack complexity&#8221; in Chirp Systems smart locks.</p>
  469. <p>&#8220;Chirp Access improperly stores credentials within its source code, potentially exposing sensitive information to unauthorized access,&#8221; CISA&#8217;s alert warned, assigning the bug a CVSS (badness) rating of 9.1 (out of a possible 10). &#8220;Chirp Systems has not responded to requests to work with CISA to mitigate this vulnerability.&#8221;</p>
  470. <p><strong>Matt Brown</strong>, the researcher CISA credits with reporting the flaw, is a senior systems development engineer at Amazon Web Services. Brown said he discovered the weakness and reported it to Chirp in March 2021, after the company that manages his apartment building started using Chirp smart locks and told everyone to install Chirp&#8217;s app to get in and out of their apartments.</p>
  471. <p>&#8220;I use Android, which has a pretty simple workflow for downloading and decompiling the APK apps,&#8221; Brown told KrebsOnSecurity. &#8220;Given that I am pretty picky about what I trust on my devices, I downloaded Chirp and after decompiling, found that they were storing passwords and private key strings in a file.&#8221;</p>
  472. <p>Using those hard-coded credentials, Brown found an attacker could then connect to an application programming interface (API) that Chirp uses which is managed by smart lock vendor <strong>August.com</strong>, and use that to enumerate and remotely lock or unlock any door in any building that uses the technology.</p>
  473. <p><strong>Update, April 18, 11:55 a.m. ET:</strong> August has provided a statement saying it does not believe August or Yale locks are vulnerable to the hack described by Brown.</p>
  474. <p>&#8220;We were recently made aware of a vulnerability disclosure regarding access control systems provided by Chirp, using August and Yale locks in multifamily housing,&#8221; the company said. &#8220;Upon learning of these reports, we immediately and thoroughly investigated these claims. Our investigation found no evidence that would substantiate the vulnerability claims in either our product or Chirp’s as it relates to our systems.&#8221;</p>
  475. <p><strong>Update, April 25, 2:45 p.m. ET:</strong> Based on feedback from Chirp, CISA has downgraded the severity of this flaw and revised their security advisory to say that the hard-coded credentials <em>do not</em> appear to expose the devices to remote locking or unlocking. CISA says the hardcoded credentials could be used by an attacker within the range of Bluetooth (~30 meters) &#8220;to change the configuration settings within the Bluetooth beacon, effectively removing Bluetooth visibility from the device.<em> This does not affect the device&#8217;s ability to lock or unlock access points</em>, and access points can still be operated remotely by unauthorized users via other means.&#8221;</p>
  476. <p><span id="more-67102"></span></p>
  477. <p>Brown said when he complained to his leasing office, they sold him a small $50 key fob that uses Near-Field Communications (NFC) to toggle the lock when he brings the fob close to his front door. But he said the fob doesn&#8217;t eliminate the ability for anyone to remotely unlock his front door using the exposed credentials and the Chirp mobile app.</p>
  478. <p>Also, the fobs pass the credentials to his front door over the air in plain text, meaning someone could clone the fob just by bumping against him with <a href="https://play.google.com/store/apps/details?id=com.wakdev.wdnfc&amp;hl=en_US&amp;gl=US" target="_blank" rel="noopener">a smartphone app</a> made to read and write NFC tags.</p>
  479. <p>Neither August nor Chirp Systems responded to requests for comment. It&#8217;s unclear exactly how many apartments and other residences are using the vulnerable Chirp locks, but multiple articles about the company from 2020 state that approximately 50,000 units use Chirp smart locks with August&#8217;s API.</p>
  480. <p>Roughly a year before Brown reported the flaw to Chirp Systems, the company was bought by <strong>RealPage</strong>, a firm founded in 1998 as a developer of multifamily property management and data analytics software. In 2021, RealPage was acquired by the private equity giant <a href="https://en.wikipedia.org/wiki/Thoma_Bravo" target="_blank" rel="noopener">Thoma Bravo</a>.</p>
  481. <p>Brown said the exposure he found in Chirp&#8217;s products is &#8220;an obvious flaw that is super easy to fix.&#8221;</p>
  482. <p>&#8220;It&#8217;s just a matter of them being motivated to do it,&#8221; he said. &#8220;But they&#8217;re part of a private equity company now, so they&#8217;re not answerable to anybody. It&#8217;s too bad, because it&#8217;s not like residents of [the affected] properties have another choice. It&#8217;s either agree to use the app or move.&#8221;</p>
  483. <p>In October 2022, <a href="https://www.propublica.org/article/yieldstar-rent-increase-realpage-rent" target="_blank" rel="noopener">an investigation</a> by <em>ProPublica</em> examined RealPage&#8217;s dominance in the rent-setting software market, and that it found &#8220;uses a mysterious algorithm to help landlords push the highest possible rents on tenants.&#8221;</p>
  484. <p>&#8220;For tenants, the system upends the practice of negotiating with apartment building staff,&#8221; ProPublica found. &#8220;RealPage discourages bargaining with renters and has even recommended that landlords in some cases accept a lower occupancy rate in order to raise rents and make more money. One of the algorithm’s developers told ProPublica that leasing agents had &#8216;too much empathy&#8217; compared to computer generated pricing.&#8221;</p>
  485. <p>Last year, the U.S. Department of Justice <a href="https://www.propublica.org/article/doj-backs-tenants-price-fixing-case-big-landlords-real-estate-tech" target="_blank" rel="noopener">threw its weight behind</a> a massive lawsuit filed by dozens of tenants who are accusing the $9 billion apartment software company of helping landlords collude to inflate rents.</p>
  486. <p>In February 2024, attorneys general for Arizona and the District of Columbia sued RealPage, alleging RealPage&#8217;s software helped create a rental monopoly.</p>
  487. ]]></content:encoded>
  488. <wfw:commentRss>https://krebsonsecurity.com/2024/04/crickets-from-chirp-systems-in-smart-lock-key-leak/feed/</wfw:commentRss>
  489. <slash:comments>41</slash:comments>
  490. </item>
  491. <item>
  492. <title>Why CISA is Warning CISOs About a Breach at Sisense</title>
  493. <link>https://krebsonsecurity.com/2024/04/why-cisa-is-warning-cisos-about-a-breach-at-sisense/</link>
  494. <comments>https://krebsonsecurity.com/2024/04/why-cisa-is-warning-cisos-about-a-breach-at-sisense/#comments</comments>
  495. <dc:creator><![CDATA[BrianKrebs]]></dc:creator>
  496. <pubDate>Thu, 11 Apr 2024 20:48:06 +0000</pubDate>
  497. <category><![CDATA[A Little Sunshine]]></category>
  498. <category><![CDATA[Data Breaches]]></category>
  499. <category><![CDATA[The Coming Storm]]></category>
  500. <category><![CDATA[Nicholas Weaver]]></category>
  501. <category><![CDATA[Sangram Dash]]></category>
  502. <category><![CDATA[Sisense breach]]></category>
  503. <category><![CDATA[U.S. Cybersecurity and Infrastructure Security Agency]]></category>
  504. <guid isPermaLink="false">https://krebsonsecurity.com/?p=67160</guid>
  505.  
  506. <description><![CDATA[The U.S. Cybersecurity and Infrastructure Security Agency (CISA) said today it is investigating a breach at business intelligence company Sisense, whose products are designed to allow companies to view the status of multiple third-party online services in a single dashboard. CISA urged all Sisense customers to reset any credentials and secrets that may have been shared with the company, which is the same advice Sisense gave to its customers Wednesday evening.]]></description>
  507. <content:encoded><![CDATA[<p>The <strong>U.S. Cybersecurity and Infrastructure Security Agency</strong> (CISA) said today it is investigating a breach at business intelligence company <strong>Sisense</strong>, whose products are designed to allow companies to view the status of multiple third-party online services in a single dashboard. CISA urged all Sisense customers to reset any credentials and secrets that may have been shared with the company, which is the same advice Sisense gave to its customers Wednesday evening.</p>
  508. <p><img decoding="async" loading="lazy" class="aligncenter wp-image-67162" src="https://krebsonsecurity.com/wp-content/uploads/2024/04/sisense.png" alt="" width="749" height="340" srcset="https://krebsonsecurity.com/wp-content/uploads/2024/04/sisense.png 1304w, https://krebsonsecurity.com/wp-content/uploads/2024/04/sisense-768x348.png 768w, https://krebsonsecurity.com/wp-content/uploads/2024/04/sisense-782x354.png 782w" sizes="(max-width: 749px) 100vw, 749px" /></p>
  509. <p>New York City based Sisense has more than a thousand customers across a range of industry verticals, including financial services, telecommunications, healthcare and higher education. On April 10, <strong>Sisense Chief Information Security Officer Sangram Dash</strong> told customers the company had been made aware of reports that &#8220;certain Sisense company information may have been made available on what we have been advised is a restricted access server (not generally available on the internet.)&#8221;</p>
  510. <p>&#8220;We are taking this matter seriously and promptly commenced an investigation,&#8221; Dash continued. &#8220;We engaged industry-leading experts to assist us with the investigation. This matter has not resulted in an interruption to our business operations. Out of an abundance of caution, and while we continue to investigate, we urge you to promptly rotate any credentials that you use within your Sisense application.&#8221;</p>
  511. <p>In its alert, CISA said it was working with private industry partners to respond to a recent compromise discovered by independent security researchers involving Sisense.</p>
  512. <p>&#8220;CISA is taking an active role in collaborating with private industry partners to respond to this incident, especially as it relates to impacted critical infrastructure sector organizations,&#8221; the sparse alert reads. &#8220;We will provide updates as more information becomes available.&#8221;</p>
  513. <p><img decoding="async" loading="lazy" class="aligncenter wp-image-67161" src="https://krebsonsecurity.com/wp-content/uploads/2024/04/cisa-sisense.png" alt="" width="750" height="688" srcset="https://krebsonsecurity.com/wp-content/uploads/2024/04/cisa-sisense.png 884w, https://krebsonsecurity.com/wp-content/uploads/2024/04/cisa-sisense-768x705.png 768w, https://krebsonsecurity.com/wp-content/uploads/2024/04/cisa-sisense-782x717.png 782w" sizes="(max-width: 750px) 100vw, 750px" /></p>
  514. <p>Sisense declined to comment when asked about the veracity of information shared by two trusted sources with close knowledge of the breach investigation. Those sources said the breach appears to have started when the attackers somehow gained access to the company&#8217;s Gitlab code repository, and in that repository was a token or credential that gave the bad guys access to Sisense&#8217;s Amazon S3 buckets in the cloud.</p>
  515. <p>Customers can use Gitlab either as a solution that is hosted in the cloud at Gitlab.com, or as a self-managed deployment. KrebsOnSecurity understands that Sisense was using the self-managed version of Gitlab.</p>
  516. <p>Both sources said the attackers used the S3 access to copy and exfiltrate several terabytes worth of Sisense customer data, which apparently included millions of access tokens, email account passwords, and even SSL certificates.</p>
  517. <p>The incident raises questions about whether Sisense was doing enough to protect sensitive data entrusted to it by customers, such as whether the massive volume of stolen customer data was ever encrypted while at rest in these Amazon cloud servers.</p>
  518. <p>It is clear, however, that unknown attackers now have all of the credentials that Sisense customers used in their dashboards.<span id="more-67160"></span></p>
  519. <p>The breach also makes clear that Sisense is somewhat limited in the clean-up actions that it can take on behalf of customers, because access tokens are essentially text files on your computer that allow you to stay logged in for extended periods of time &#8212; sometimes indefinitely. And depending on which service we&#8217;re talking about, it may be possible for attackers to re-use those access tokens to authenticate as the victim without ever having to present valid credentials.</p>
  520. <p>Beyond that, it is largely up to Sisense customers to decide if and when they change passwords to the various third-party services that they&#8217;ve previously entrusted to Sisense.</p>
  521. <p>Earlier today, a public relations firm working with Sisense reached out to learn if KrebsOnSecurity planned to publish any further updates on their breach (KrebsOnSecurity posted a screenshot of the CISO&#8217;s customer email to both <a href="https://www.linkedin.com/posts/bkrebs_there-is-something-potentially-huge-popping-activity-7183982303784620033-T3wd?utm_source=share&amp;utm_medium=member_desktop" target="_blank" rel="noopener">LinkedIn</a> and <a href="https://infosec.exchange/@briankrebs/112249710611213991" target="_blank" rel="noopener">Mastodon</a> on Wednesday evening). The PR rep said Sisense wanted to make sure they had an opportunity to comment before the story ran.</p>
  522. <p>But when confronted with the details shared by my sources, Sisense apparently changed its mind.</p>
  523. <p>&#8220;After consulting with Sisense, they have told me that they don&#8217;t wish to respond,&#8221; the PR rep said in an emailed reply.</p>
  524. <p><strong>Update, 6:49 p.m., ET:</strong> Added clarification that Sisense is using a self-hosted version of Gitlab, not the cloud version managed by Gitlab.com. </p>
  525. <p>Also, Sisense&#8217;s CISO Dash just sent an update to customers directly. The latest advice from the company is far more detailed, and involves resetting a potentially large number of access tokens across multiple technologies, including Microsoft Active Directory credentials, GIT credentials, web access tokens, and any single sign-on (SSO) secrets or tokens. </p>
  526. <p>The full message from Dash to customers is below:</p>
  527. <p>&#8220;Good Afternoon,</p>
  528. <p>We are following up on our prior communication of April 10, 2024, regarding reports that certain Sisense company information may have been made available on a restricted access server. As noted, we are taking this matter seriously and our investigation remains ongoing.</p>
  529. <p>Our customers must reset any keys, tokens, or other credentials in their environment used within the Sisense application.</p>
  530. <p>Specifically, you should:<br />
  531. &#8211; Change Your Password: Change all Sisense-related passwords on http://my.sisense.com<br />
  532. &#8211; Non-SSO:<br />
  533.    &#8211; Replace the Secret in the Base Configuration Security section with your GUID/UUID.<br />
  534.    &#8211; Reset passwords for all users in the Sisense application.<br />
  535.    &#8211; Logout all users by running GET /api/v1/authentication/logout_all under Admin user.<br />
  536. &#8211; Single Sign-On (SSO):<br />
  537.    &#8211; If you use SSO JWT for the user’s authentication in Sisense, you will need to update sso.shared_secret in Sisense and then use the newly generated value on the side of the SSO handler.<br />
  538.    &#8211; We strongly recommend rotating the x.509 certificate for your SSO SAML identity provider.<br />
  539.    &#8211; If you utilize OpenID, it’s imperative to rotate the client secret as well.<br />
  540.    &#8211; Following these adjustments, update the SSO settings in Sisense with the revised values.<br />
  541.    &#8211; Logout all users by running GET /api/v1/authentication/logout_all under Admin user.<br />
  542. &#8211; Customer Database Credentials: Reset credentials in your database that were used in the Sisense application to ensure continuity of connection between the systems.<br />
  543. &#8211; Data Models: Change all usernames and passwords in the database connection string in the data models.<br />
  544. &#8211; User Params: If you are using the User Params feature, reset them.<br />
  545. &#8211; Active Directory/LDAP: Change the username and user password of users whose authorization is used for AD synchronization.<br />
  546. &#8211; HTTP Authentication for GIT: Rotate the credentials in every GIT project.<br />
  547. &#8211; B2D Customers: Use the following API PATCH api/v2/b2d-connection in the admin section to update the B2D connection.<br />
  548. &#8211; Infusion Apps: Rotate the associated keys.<br />
  549. &#8211; Web Access Token: Rotate all tokens.<br />
  550. &#8211; Custom Email Server: Rotate associated credentials.<br />
  551. &#8211; Custom Code: Reset any secrets that appear in custom code Notebooks.</p>
  552. <p>If you need any assistance, please submit a customer support ticket at https://community.sisense.com/t5/support-portal/bd-p/SupportPortal and mark it as critical. We have a dedicated response team on standby to assist with your requests.</p>
  553. <p>At Sisense, we give paramount importance to security and are committed to our customers’ success. Thank you for your partnership and commitment to our mutual security.</p>
  554. <p>Regards,</p>
  555. <p>Sangram Dash<br />
  556. Chief Information Security Officer&#8221;</p>
  557. ]]></content:encoded>
  558. <wfw:commentRss>https://krebsonsecurity.com/2024/04/why-cisa-is-warning-cisos-about-a-breach-at-sisense/feed/</wfw:commentRss>
  559. <slash:comments>33</slash:comments>
  560. </item>
  561. </channel>
  562. </rss>
  563.  
  564. <!--
  565. Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/
  566.  
  567. Object Caching 209/209 objects using memcached
  568. Page Caching using memcached
  569. Database Caching using memcached
  570.  
  571. Served from: krebsonsecurity.com @ 2024-05-17 22:48:13 by W3 Total Cache
  572. -->

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//feeds.feedburner.com/krebsonsecurity/TEjH

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda