Is your PHP version at risk of PHP2Shell RCE? Check Free Now
Alleged

Latham & Watkins Data Breach

Published: Oct 19, 2026 Silent Ransom Group

Threat Level

High

Confidence: High

Quick Summary

Company
Latham & Watkins Data Breach
Industry
Legal Services
Threat Actor
Silent Ransom Group
Date of Incident
Oct 19, 2026

Executive Summary

Silent Ransom Group (SilentRansomGroup) listed Latham & Watkins (lw[.]com) on its extortion site on October 19, 2026, with the listing identified by the SOCRadar Dark Web Team. Latham & Watkins is a US-based firm and one of the world’s largest law practices, advising corporations, financial institutions, and governments on M&A transactions, regulatory proceedings, and litigation. The firm’s files contain some of the most commercially sensitive communications in existence, and that sensitivity is central to its exposure: Silent Ransom Group targets organizations where data sensitivity amplifies extortion leverage, and a global law firm holding privileged client communications fits that model precisely. Silent Ransom Group operates as an extortion-focused group whose business model centers on data theft, and its primary access tactic is callback phishing and social engineering rather than infostealer-driven initial access. That approach shapes the current claim: the group seeks material whose exposure creates maximum pressure, and a law firm’s privileged client files offer exactly that leverage. As with all listings on ransomware leak and extortion sites, the claim cannot always be verified and may not reflect a confirmed breach, so it should be treated as alleged pending confirmation.

Technical Analysis

SOCRadar’s stealer-log query against lw[.]com returned a mixed picture with a notably tight timeline. The telemetry identified 9 records containing internal @lw.com employee credentials on the primary lw[.]com domain, 11 records belonging to external users — customers, partners, or vendors — accessing lw[.]com, and additional records showing employee credentials reused on third-party consumer and SaaS services, a pattern consistent with workstation infection. Freshness is the most consequential finding: the exposed credentials fall within October 7–16, 2026, a ten-day window of stealer activity that ended three days before the extortion listing. Credential exposure this fresh and this close to the listing date warrants immediate action, independent of whether the stealer logs connect to this specific incident. The telemetry does not establish how Silent Ransom Group gained access, and the two findings should not be conflated. SRG’s primary tactic is callback phishing and social engineering — not infostealer-driven initial access — so the stealer-log exposure and the extortion listing may be parallel risks rather than cause and effect. They are best treated as two separate investigations: first, rotate and audit all employee credentials appearing in the October 7–16 window; second, activate incident response for the extortion claim itself, because data theft is SRG’s business model and the firm should assume exfiltration occurred until forensics says otherwise. Depending on what data SRG claims to hold, client notification obligations under privilege and confidentiality agreements may apply, adding a legal and compliance dimension to the technical response. Continued dark web and stealer-log monitoring will help determine whether additional Latham & Watkins credentials surface, while proactive credential-hygiene checks across lw[.]com and password rotation for the exposed October 7–16 accounts should proceed without waiting for forensic conclusions on the extortion claim.

Disclaimer

This report is intended for threat intelligence and security awareness purposes. SOCRadar does not host, redistribute or buy stolen data. All breach information reported here is collected from publicly accessible threat actor and ransomware portals. This content is intended to equip CTI teams with context around recent attacks. While we strive for accuracy, listings on ransomware leak and extortion sites cannot always be independently verified and may not reflect confirmed breaches. If you believe any data in this report is incorrect, please contact us.

Share

LinkedIn