Nvidia sued for stealing trade secrets: blunder showed rival company's code
Nvidia is being sued after an engineer hired from automotive supplier Valeo was found with 6GB of Valeo’s source code and documentation, allegedly stolen before he left and later exposed during a joint screen-sharing session. Commenters argue over whether this represents a rogue employee or potential corporate negligence, touching on how far a company’s responsibility extends when hired staff bring proprietary material from previous jobs. The exchange broadens into concerns about trade secret theft in tech, the legal line between using experience and copying code, and how practices like code reuse, open-source scanning, and AI-assisted development complicate intellectual property risk.
Corporate Responsibility and “Who Knew?”
- Debate over when a corporation “knows” about wrongdoing.
- One side: unless managers/executives knew or encouraged it, liability should largely fall on the individual.
- Other side: managers are responsible for what their reports do; even ignorance is a failure of oversight, and big companies shouldn’t get a pass for being “too big to know.”
- Some argue even one complicit manager is enough to attribute knowledge to the company.
Hiring from Competitors vs. Stealing IP
- Widely accepted that hiring for domain experience is normal and legal.
- Sharp distinction drawn between using accumulated expertise vs. copying source code or design files.
- “Inevitable disclosure” (experience == trade secret) is rejected by most commenters as incompatible with employee mobility.
- Memorized knowledge is generally seen as acceptable; copying files is not.
Facts and Severity of the Alleged Misconduct
- Discussion stresses that this goes beyond a casual snippet: claims of unauthorized access, tens of thousands of files, ~6GB of code, and printed docs and hardware at home.
- Some think this is clearly an individual’s long-running IP theft pattern; others still question whether any Nvidia management encouraged, leveraged, or simply failed to detect it.
- Unclear from the thread whether stolen code was actually merged into Nvidia’s repositories or only used as reference.
Prevalence of Code Reuse and Whistleblower Risks
- Several note that copying code between employers, or keeping private libraries/snippets, is common but usually hidden.
- Often handled quietly by low-level managers; rarely escalated to executives.
- Whistleblowers face social and career risk for reporting IP misuse, even where laws nominally protect them.
Nvidia’s IP Posture and Open-Source Image
- Some argue large firms are “allergic” to tainted IP and invest heavily in audits and source scanning to avoid lawsuits.
- Others say incentives and willful blindness mean illegal reuse still happens.
- Dispute over Nvidia’s attitude to free software: critics emphasize proprietary drivers/firmware; defenders point to hundreds of open-source repos and contributions, and note the industry-wide reliance on proprietary firmware.
AI Tools and Future IP Leakage
- Concern that LLM-based tools may inadvertently regurgitate proprietary code from prior training, blurring lines between “experience” and copying.
- Some companies respond with blanket bans on such tools to avoid IP contamination.