Everest Ransomware Leaks 1TB of Stolen ASUS Data

[Brownie2019]

Content source

https://hackread.com/everest-ransomware-asus-data-leak/

On December 2, 2025, Hackread.com exclusively reported that the Everest ransomware group claimed to have stolen 1TB of sensitive ASUS data, including information related to the company’s AI models, memory dumps, and calibration files. ASUS later confirmed the report and acknowledged the breach, attributing it to a third-party vendor.

Everest has now leaked the entire dataset online. The release followed the group’s claim that ASUS failed to meet the deadline to initiate contact. Notably, the ransomware gang had given the tech giant 24 hours to respond, following its usual approach of demanding a ransom.
As noted by Hackread.com, the leaked data is now circulating on various Russian-language cybercrime forums, including Exploit and DamageLib (formerly and now seized XSS.IS). According to the hackers, the 1TB dump contains nine files, some of which appear to be from ArcSoft and Qualcomm. However, Hackread.com did not download or analyze the leaked material.

This latest leak is part of a series of breaches recently carried out by the Everest ransomware group. Over Christmas, the Russia-linked gang claimed to have breached Chrysler, the American automaker, stating it had stolen 1TB of data. The group described it as a complete database tied to Chrysler operations, along with more than 105GB of Salesforce-related information.

In November 2025, the ransomware group claimed responsibility for breaching Under Armour, stealing 343GB of data, which it later leaked online. The company is now facing multiple lawsuits as a result of the breach. Additional breaches, leaks, and claims by the Everest ransomware group can be found here.
Everest’s latest leak adds to a growing list of big-name targets, and the group shows no signs of slowing down. For ASUS and other companies hit in recent months, the focus should be figuring out exactly what was exposed and increasing their security before it happens again.

 

[Bot]

The text you quoted appears to be from Hackread’s piece published on December 31, 2025 about Everest allegedly leaking a ~1TB ASUS dataset after first claiming the theft on December 2, 2025. ([hackread.com](https://hackread.com/everest-ransomware-asus-data-leak/?utm_source=openai))

What’s confirmed vs. what’s still “attacker-claimed”

• Public reporting supports that ASUS acknowledged an incident tied to a third-party/supplier, rather than (at least publicly) stating ASUS’s own core infrastructure was compromised. ([hackread.com](https://hackread.com/everest-ransomware-asus-data-leak/?utm_source=openai))
• The “1TB leaked dataset” details are coming from the ransomware actor and secondary reporting. Hackread explicitly notes it did not download/analyze the leaked material. ([hackread.com](https://hackread.com/everest-ransomware-asus-data-leak/?utm_source=openai))
• Some reporting around the same timeframe says ASUS indicated no customer/employee data was involved (but that can only be treated as the company’s statement unless independently validated). ([yahoo.com](https://www.yahoo.com/news/articles/asus-faces-hack-involving-company-155614913.html?utm_source=openai))

Why this matters to regular users (even if “no customer data” is claimed)

• If source code/internal tooling is truly exposed, it can sometimes help attackers craft more convincing phishing, social-engineering, or research for future attacks. (It does not automatically mean your ASUS device is compromised.)
• The most realistic near-term risk to end users is usually scams and phishing exploiting the news cycle (fake “ASUS security update” emails, fake driver sites, “support” calls, etc.).

Safe, practical steps for forum members

• Do not download any “leaked ASUS files” to “check” them. Besides legal/ethical issues, leak packs are a common malware delivery vehicle.
• Be strict about download sources: only get BIOS/firmware/drivers/utilities from ASUS’s official channels (or your device OEM portal if it’s a rebadged system).
• Treat “ASUS breach” themed messages as suspicious: verify sender domains, don’t open unexpected attachments, don’t follow email links for “urgent patches.”
• Basic account hygiene: enable MFA where possible and change passwords if you reused them across sites (this is general best practice; there’s no public proof from the sources above that consumer account databases were taken).

If you want to take this further on MalwareTips

If anyone receives a suspicious “ASUS update / breach notice” email, or finds a questionable download claiming to be related to this leak, post the headers/URL (safely) and/or submit the file/URL to VirusTotal and share the link so the community can review it without guessing.

Key takeaway: based on current reporting, this is primarily a supplier/third-party incident with attacker claims of a large leak; the safest user response is phishing vigilance + only using official update channels. ([hackread.com](https://hackread.com/everest-ransomware-asus-data-leak/?utm_source=openai))