This article is more than 1 year old
Leaked stolen Nvidia key can sign Windows malware
70k staff email addresses and NTLM password hashes also dumped online
The private key of an Nvidia code-signing certificate was among the mountain of files stolen and leaked online by criminals who ransacked the GPU giant's internal systems.
At least two binaries not developed by Nvidia, but signed this week with its stolen key, making them appear to be Nvidia programs, have appeared in malware sample database VirusTotal.
This leak means sysadmins should take steps, or review their security policies and defenses, to ensure code recently signed by the rogue cert is detected and blocked as it is most likely going to be malicious. This can be done through Windows configuration, network filtering rules, or whatever you use to police your organization.
Computer security bod Bill Demirkapi – who we've featured before on these pages – tweeted a warning about the certificate key potentially being used to sign Windows kernel-level driver files:
As part of the #NvidiaLeaks, two code signing certificates have been compromised. Although they have expired, Windows still allows them to be used for driver signing purposes. See the talk I gave at BH/DC for more context on leaked certificates: https://t.co/UWu3AzHc66 pic.twitter.com/gCrol0BxHd— Bill Demirkapi (@BillDemirkapi) March 3, 2022
In later tweets he added that Windows will accept drivers signed with certificates issued prior to July 29, 2015 without a timestamp. Microsoft's Windows driver signing policy corroborates this, stating the operating system will run drivers "signed with an end-entity certificate issued prior to July 29th 2015 that chains to a supported cross-signed CA".
The leaked Nvidia certificate key is just such a creature, having expired in 2014. Code signed with this key will, in the right conditions, be accepted by Windows even though the key has expired. Another Nvidia cert was leaked though expired after the cut-off date.
We asked Microsoft what steps would it be willing to take to ensure Windows blocks all code signed by the 2014 cert since its leak. A spokesperson told us: "We are looking into these new claims and we will do what is necessary to keep our customers protected."
Infosec bod Kevin Beaumont spotted some folks have been signing their own driver code with Nvidia's private 2014 key and uploading it to VirusTotal to check if antivirus scanners accepted it. He posted on Twitter:
VirusTotal search if you want 'em— Kevin Beaumont (@GossiTheDog) March 4, 2022
ls:"2022-03-01T00:00:00+" signature:43BB437D609866286DD839E1D00309F5 p:1+ tag:signed
.sys (drivers) load fine in Windows 10/11 still, even when signed with expired cert.
Threat actors started on 1st March, a day after torrent posted. pic.twitter.com/S6pCfgV8hb
The move to allow such drivers was a backwards compatibility effort (per an MSDN post from 2015, introducing Windows 10 build 1607) to prevent a then-new Windows 10 feature from causing problems with previously unsigned drivers.
We note that a good number of antivirus scanners, tested by VirusTotal on uploaded samples, are now seemingly catching code signed by the rogue Nvidia certificate, so it may be that your AV engine will automatically block it.
- Data stolen from Nvidia, blueprints leak threatened
- Nvidia, Apple noticeably absent from Intel-led chiplet interconnect collaboration
- Conti ransomware gang leak: 60,000 messages online
- Insurance giant Aon confirms it has suffered 'cyber incident'
The crooks who compromised Nvidia's internal systems to steal and leak the certificate key – among many other files, including credentials, secret source code, and documentation – call themselves Lapsus$, and are seemingly trying to blackmail Nvidia into removing cryptomining limit from its GPU firmware. Last year, for its RTX 30-series graphics cards, Nvidia introduced a technology into their drivers called Lite Hash Rate, or LHR for short.
LHR cripples cryptocurrency mining. By nerfing the cards' cryptomining performance, Nvidia hoped to make its graphical processing units less attractive to miners, leaving more hardware available to gamers, in theory, and others who actually want graphics performance rather than pure hash rates.
Lapsus$, according to the group's Telegram page, are threatening Nvidia with the public release of more internal materials and details of chip blueprints unless the company promises to remove LHR. It seems wholly implausible that Nvidia would give in to such blackmail. The gang also wants Nvidia to open-source its drivers for Macs, Linux, and Windows PCs.
According to Have I Been Pwned, within the leaked data are "over 70,000 employee email addresses and NTLM password hashes, many of which were subsequently cracked and circulated within the hacking community."
In a statement Nvidia previously said: "We are aware that the threat actor took employee passwords and some Nvidia proprietary information from our systems and has begun leaking it online. Our team is working to analyze that information." It is maintaining an incident response page here. ®