/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Nvidia confirms hackers have leaked employee data and “some Nvidia proprietary information”; LAPSUS$ group claims it took 1TB data, including DLSS source code

Michael Kan / PCMag :

PCMag Michael Kan

Context & Ripple Effects

Nvidia’s confirmation established that the LAPSUS$ intrusion reached both employee data and proprietary material, while the group’s claim about DLSS source code remained an allegation. The episode widened quickly: more than 71,000 employee credentials were reported stolen, turning a corporate IP breach into a risk for Nvidia staff accounts.

LAPSUS$ also tried to use the theft as leverage, demanding changes to Nvidia’s mining limits and GPU-driver source availability. Subsequent reports that leaked code-signing certificates were used to sign Windows malware showed the incident’s impact extending beyond disclosure of files.

First-order effects

  • Nvidia must contain exposure of employee identities and credentials while assessing which proprietary materials were taken and leaked.
  • Nvidia employees whose credentials were included in the reported haul face account-security risk, particularly where password hashes have been cracked and circulated.

Second-order effects

  • The leaked signing certificates give malware operators a way to make malicious Windows tools appear more trustworthy, increasing the security burden on Nvidia and affected Windows users.
  • LAPSUS$’ public demands turn stolen source code and internal data into bargaining tools, pressuring Nvidia over product controls and driver policy rather than solely seeking a ransom.

Third-order effects

  • The incident illustrates how a single corporate compromise can combine identity theft, intellectual-property leakage, and software-supply-chain abuse when code-signing assets are exposed.
  • If this pattern persists, chip and software vendors will need to treat employee identity systems and signing infrastructure as core protections for proprietary technology, not separate security domains.

The trend: High-profile intrusions are increasingly monetizing both stolen corporate data and the trusted software credentials that can enable follow-on attacks.

Discussion

  • @vxunderground @vxunderground on x
    LAPSU$ extortion group, a group operating out of South America, claim to have breached NVIDIA and exfiltrated over 1TB of proprietary data. LAPSU$ claims NVIDIA performed a hack back and states NVIDIA has successful ransomed their machines Intel and photos courtesy of @S0ufi4n3 h…
  • @brettcallow Brett Callow on x
    Lapsus$ claim responsibility for the hack on Nvidia - and also claim that Nvidia successfully hacked back. https://twitter.com/...
  • @luigiblood @luigiblood on x
    They said Nvidia DLSS source code leaked except I instantly see “nvn2” in the screenshot which sounds... Switch 2 specific code? https://www.techpowerup.com/ ...
  • @joncomms Jon Cartwright on x
    AMD: https://twitter.com/... https://twitter.com/...
  • @videocardz @videocardz on x
    DLSS is now open-source 🙃 https://twitter.com/...
  • @malwaretechblog Marcus Hutchins on x
    To me this sounds a lot like LAPSUS$ installed Nvidia's corporate agent on their own machine then triggered a data loss prevention policy, which they mistook for ransomware because they're morons. https://twitter.com/...
  • @lkarlslund Lars Karlslund on x
    LAPSUS is threatening to release 1TB of stolen data from NVIDIA, which is the equivalent of the last three driver updates I downloaded for my graphics card https://twitter.com/...
  • @malwaretechblog Marcus Hutchins on x
    People are reporting the Nvidia hack is ransomware. I've not personally verified the data or claims, but I've seen similar screenshots from the same chat shared by multiple different Twitter accounts. https://twitter.com/...
  • @stockmktnewz @stockmktnewz on x
    Nvidia $NVDA said today a hacker leaked employee credentials and some company proprietary information online according to Reuters https://twitter.com/...
  • @stockmktnewz @stockmktnewz on x
    “We have no evidence of ransomware being deployed on the Nvidia environment or that this is related to the Russia-Ukraine conflict” - Nvidia spokesperson Nvidia is analyzing the information that has been leaked and does not anticipate any disruption to the company's business.