{"id":18064,"date":"2022-03-02T13:49:10","date_gmt":"2022-03-02T13:49:10","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/03\/02\/nvidia-hack-continues-with-release-of-dlss-source-code\/"},"modified":"2022-03-02T13:49:10","modified_gmt":"2022-03-02T13:49:10","slug":"nvidia-hack-continues-with-release-of-dlss-source-code","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/03\/02\/nvidia-hack-continues-with-release-of-dlss-source-code\/","title":{"rendered":"Nvidia Hack Continues with Release of DLSS Source Code"},"content":{"rendered":"

<\/a>\n<\/p>\n

This site may earn affiliate commissions from the links on this page. Terms of use<\/a>.<\/div>\n
\n
\n
\n \t \t \"\"<\/div>\n<\/p><\/div>\n

Following last week\u2019s cyber attack on Nvidia by a group of hackers named Lapsus$, news has been dripping out about what kind of data the hackers were able to grab, and what they intend to do with it.\u00a0 The group has now leaked what appears to be the source code for Nvidia\u2019s Deep Learning Super Sampling (DLSS) technology. That\u2019s the proprietary tech that uses AI and an Nvidia GPU\u2019s tensor cores to improve rendering performance in supported games.<\/p>\n

The news of the leak comes from an anonymous source who sent a screenshot of the illicit files to TechPowerUp<\/a>. The leaked files seem to include C++ files and assets, along with a \u201cDSLL Programming Guide,\u201d seemingly made to help developers implement it properly. Despite the embarrassing release of a company\u2019s proprietary source code, developers working on alternatives from the company\u2019s competitors will probably avoid it like the plague.<\/p>\n

Both AMD and Intel have their own version of this technology, named FidelityFX Super Resolution (FSR) and Intel Xe Super Sampling (XeSS), but it\u2019s unlikely any serious programmer from either company would even glance at the forbidden fruit out of fear of legal retribution. That standard, however, might not apply to non US actors. Nvidia would likely act with extreme prejudice to protect its IP, so digging into material like this is still potentially risky.<\/p>\n

\"\"<\/p>\n

The alleged DLSS source code files. (Image: TechPowerUp)<\/p>\n<\/div>\n

In response, Nvidia released a statement confirming the breach and including several additional details to a German site named Hardwareluxx<\/a>. The statement reads, \u201cOn February 23, 2022, NVIDIA became aware of a cybersecurity incident which impacted IT resources. Shortly after discovering the incident, we further hardened our network, engaged cybersecurity incident response experts, and notified law enforcement.<\/em><\/p>\n

We have no evidence of ransomware being deployed on the NVIDIA environment or that this is related to the Russia-Ukraine conflict. However, we are aware that the threat actor took employee credentials and some NVIDIA proprietary information from our systems and has begun leaking it online. Our team is working to analyze that information. We do not anticipate any disruption to our business or our ability to serve our customers as a result of the incident.<\/em><\/p>\n

Security is a continuous process that we take very seriously at NVIDIA \u2013 and we invest in the protection and quality of our code and products daily.\u201d<\/em><\/p>\n

This news is an escalation in the skirmish between Nvidia and the hacking group, which had previously came forward to declare they were just trying to help out miners and gamers by stealing code to dismantle the company\u2019s Lite Hash Rate technology in order to allow the crypto miners of the world to throw off the shackles of the hash rate limiter it included with its 30-series GPUs. The hackers also reportedly began selling a workaround<\/a>. It remains to be seen what the next step might be, but the hackers have proclaimed they stole 1TB of confidential data from Nvidia\u2019s servers before being shut out, and have said if Nvidia removes the LHR limiter from its GPU they will forget all about the stolen data.<\/p>\n

Now Read:<\/strong><\/p>\n<\/div>\n