Everest Ransomware Group Claims Nissan Data Breach and Extortion Deadline
The Everest ransomware group claimed it breached Nissan Motor Corporation and stole data, posting alleged proof on its dark web leak site. The actors shared six screenshots and a directory listing that appear to show internal file storage and records, including documents and data extracts in formats such as .csv, .txt, and .xls (with additional file types like .pgp referenced). The material shown includes references to dealership information, certification reports, and claims processing; one screenshot reportedly shows a spreadsheet with dealership names and locations. Everest issued Nissan a five-day ultimatum to respond, threatening to publish the allegedly stolen data if the company does not engage.
The screenshots do not visibly expose sensitive personal data, but the folder names and file types suggest access to operational systems and internal documentation that could enable further exploitation or data mining. Reporting also contextualized the claim against Nissan’s prior exposure to ransomware activity, including a 2025 claim by Qilin involving a Nissan-related entity, underscoring continued targeting of large automotive organizations by extortion-focused groups.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
5 events from the most recent confirmed update back to the earliest known activity.
Nissan says alleged breach stemmed from third-party vendor incident
Nissan Motor Co. said the reported breach claims were linked to a cyber incident at a third-party vendor rather than Nissan's internal environment. The company added that its internal systems and customer data were not affected.
ASEC roundup cites Everest attack on major Japanese automaker
AhnLab ASEC's weekly dark web roundup noted an Everest ransomware attack against a major Japanese automobile manufacturing and sales company, consistent with the Nissan claim. This reflected broader security-industry reporting of the incident in mid-January.
Nissan had not publicly responded as reports emerged
By the time media reports were published, Nissan had not issued a public response to Everest's allegations. Coverage on January 12 and January 13 repeated the same claimed breach and extortion deadline without confirming the intrusion independently.
Everest gives Nissan a five-day deadline to respond
Alongside its breach claim, Everest reportedly demanded that Nissan respond within five days or the group would publish the allegedly stolen data. The visible screenshots suggested access to dealership, reporting, and operational records, though no clear sensitive personal data was exposed in the images.
Everest posts Nissan breach claim on leak site
On its dark web leak site, the Everest ransomware group claimed it had breached Nissan Motor Corporation. The post included six screenshots and a directory listing purportedly showing Nissan-related internal files and folders.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
4 references tracked. Mallory keeps watching after this page renders.
teiss - News - Nissan says alleged data breach linked to third-party vendor, not internal systems
teiss.co.uk
Open sourceRansom & Dark Web Issues Week 2, January 2026 - ASEC
asec.ahnlab.com
Open sourceEverest ransomware group claims Nissan breach, demands response | SC Media
scworld.com
Open sourceEverest Ransomware Claims Breach at Nissan, Says 900GB of Data Stolen
hackread.com
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


