Skip to main content

Ransomware gang caught using Microsoft-approved drivers to hack targets

Security researchers say they have evidence that threat actors affiliated with the Cuba ransomware gang used malicious hardware drivers certified by Microsoft during an recent attempted ransomware attack.

Drivers — the software that allows operating systems and apps to access and communicate with hardware devices — require highly privileged access to the operating system and its data, which is why Windows requires drivers to bear an approved cryptographic signature before it will allow the driver to load.

These drivers have long been abused by cybercriminals, often taking a “bring your own vulnerable driver” approach, in which hackers exploit vulnerabilities found within an existing Windows driver from a legitimate software publisher. Researchers at Sophos say they have observed hackers making a concerted effort to progressively move towards using more widely trusted digital certificates.

While investigating suspicious activity on a customer network, Sophos discovered evidence that the Russia-linked Cuba ransomware gang are making efforts to move up the trust chain. During their investigation, Sophos found that the gang’s oldest malicious drivers dating back to July were signed by certificates from Chinese companies, then began signing their malicious driver with a leaked, since-revoked Nvidia certificate found in the data dumped by the Lapsus$ ransomware gang when it hacked the chipmaker in March.

The attackers have now managed to obtain “signage” from Microsoft’s official Windows Hardware Developer Program, which means the malware is inherently trusted by any Windows system.

“Threat actors are moving up the trust pyramid, attempting to use increasingly more well-trusted cryptographic keys to digitally sign their drivers,” wrote Sophos researchers Andreas Klopsch and Andrew Brandt in a blog post. “Signatures from a large, trustworthy software publisher make it more likely the driver will load into Windows without hindrance, improving the chances that Cuba ransomware attackers can terminate the security processes protecting their targets’ computers.”

Sophos found that the Cuba gang planted the malicious signed driver onto a targeted system using a variant of the so-called BurntCigar loader, a known piece of malware affiliated with the ransomware group that was first observed by Mandiant. The two are used in tandem in an attempt to disable endpoint detection security tools on the targeted machines.

If successful — which, in this case, they were not — the attackers could deploy the ransomware on the compromised systems.

Sophos, along with researchers from Mandiant and SentinelOne, informed Microsoft in October that drivers certified by legitimate certificates were used maliciously in post-exploitation activity. Microsoft’s own investigation revealed that several developer accounts for the Microsoft Partner Center were engaged in submitting malicious drivers to obtain a Microsoft signature.

“Ongoing Microsoft Threat Intelligence Center analysis indicates the signed malicious drivers were likely used to facilitate post-exploitation intrusion activity such as the deployment of ransomware,” Microsoft said in an advisory published as part of its monthly scheduled release of security patches, known as Patch Tuesday. Microsoft said it has released Windows security updates revoking the certificate for affected files and has suspended the partners’ seller accounts.

Earlier this month, a U.S. government advisory revealed that the Cuba ransomware gang has brought in an additional $60 million from attacks against 100 organizations globally. The advisory warned that the ransomware group, which has been active since 2019, continues to target U.S. entities in critical infrastructure, including financial services, government facilities, healthcare and public health, and critical manufacturing and information technology.

Ransomware gang caught using Microsoft-approved drivers to hack targets by Carly Page originally published on TechCrunch



source https://techcrunch.com/2022/12/13/cuba-ransomware-microsoft-drivers/

Comments

Popular posts from this blog

Max Q: Psyche(d)

In this issue: SpaceX launches NASA asteroid mission, news from Relativity Space and more. © 2023 TechCrunch. All rights reserved. For personal use only. from TechCrunch https://ift.tt/h6Kjrde via IFTTT

Max Q: Anomalous

Hello and welcome back to Max Q! Last week wasn’t the most successful for spaceflight missions. We’ll get into that a bit more below. In this issue: First up, a botched launch from Virgin Orbit… …followed by one from ABL Space Systems News from Rocket Lab, World View and more Virgin Orbit’s botched launch highlights shaky financial future After Virgin Orbit’s launch failure last Monday, during which the mission experienced an  “anomaly” that prevented the rocket from reaching orbit, I went back over the company’s financials — and things aren’t looking good. For Virgin Orbit, this year has likely been completely turned on its head. The company was aiming for three launches this year, but everything will remain grounded until the cause of the anomaly has been identified and resolved. It’s unclear how long that will take, but likely at least three months. Add this delay to Virgin’s dwindling cash reserves and you have a foundation that’s suddenly much shakier than before. ...

What’s Stripe’s deal?

Welcome to  The Interchange ! If you received this in your inbox, thank you for signing up and your vote of confidence. If you’re reading this as a post on our site, sign up  here  so you can receive it directly in the future. Every week, I’ll take a look at the hottest fintech news of the previous week. This will include everything from funding rounds to trends to an analysis of a particular space to hot takes on a particular company or phenomenon. There’s a lot of fintech news out there and it’s my job to stay on top of it — and make sense of it — so you can stay in the know. —  Mary Ann Stripe eyes exit, reportedly tried raising at a lower valuation The big news in fintech this week revolved around payments giant Stripe . On January 26, my Equity Podcast co-host and overall amazingly talented reporter Natasha Mascarenhas and I teamed up to write about how Stripe had set a 12-month deadline for itself to go public, either through a direct listing or by pursuin...