HEC Group was listed on 24 September 2026 by the dragonforce ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). dragonforce listed 12 organizations that month and 666 in total.
- Listed 55 days ago.
- 874 organizations were listed by all groups in September 2026, see the month.
- 139 in Technology that month.
- 7 in TW that month.
Updated 2026-11-18 11:12 UTC. Data: public leak-site listings. How we work.
Threat Group Post & Evidence
- Listed by
- Dragonforce 666 listings in total
The listing states no data size and no ransom demand.
No capture of the original post
We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.
The group's leak-site address is on paid plans
Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
On August 30, HEC Group issued an official statement addressed to shareholders of TPE:3032 and other stakeholders, announcing that the company had been the target of a cyberattack. In its statement, the company claimed that the breach was detected immediately, that high-tech countermeasures were deployed, and that no corporate documentation was lost. The incident was characterized as a minimal, random occurrence. The reality, however, is starkly different. Our operation against the company began weeks prior to that publication. Due to a systemic failure to implement basic security principles, we gained nearly total control over the infrastructure supporting the development and commercial operations of the entire corporate group. We conducted a methodical and comprehensive review of the documentation, exfiltrating a vast amount of data. We remained undetected for as long as necessary to s…
Show the full post (2411 characters)
On August 30, HEC Group issued an official statement addressed to shareholders of TPE:3032 and other stakeholders, announcing that the company had been the target of a cyberattack. In its statement, the company claimed that the breach was detected immediately, that high-tech countermeasures were deployed, and that no corporate documentation was lost. The incident was characterized as a minimal, random occurrence. The reality, however, is starkly different. Our operation against the company began weeks prior to that publication. Due to a systemic failure to implement basic security principles, we gained nearly total control over the infrastructure supporting the development and commercial operations of the entire corporate group. We conducted a methodical and comprehensive review of the documentation, exfiltrating a vast amount of data. We remained undetected for as long as necessary to secure everything we sought. Only after completing our objectives did we initiate the data encryption process, the company's technical staff did not even detect our presence until many hours later. At the time of their official announcement, HEC Group's leadership knew the statement was entirely false. Its sole purpose was to manipulate stock market trading. Instead of contacting us to mitigate the damage, management chose to deceive the exchange. When we finally managed to contact the company's leadership and offered them a chance to make their official statement more truthful in exchange for the deletion of the taken documents, they showed no interest. If the leadership of HEC Group has decided to pursue a path of selfdestruction, we will not stand in their way. To prove that HEC Group’s statement was a fabrication and that our claims are accurate, we will now publish a portion of the exfiltrated data. This initial release will consist of over 360,000 files, drawn from a total volume measuring in terabytes. This data will provide stock exchange regulators and partner companies with exhaustive evidence of the actual events. The remaining documents will not be released publicly at this time, as we have devised a more strategic use for them. While the countdown timer below this publication runs, the companies affiliated with HEC Group, their shareholders, and regulatory authorities have time to prepare. HEC Group has one final opportunity to accept our proposal and avoid the consequences.
Amounts as written
- 360,000 files
Kinds of data mentioned
-
Email and communications
“…contacting us to mitigate the damage, management chose to deceive the exchange. When we finally managed to contact the company's leadership and offered them a chance to…”
-
Employee and HR records
“…objectives did we initiate the data encryption process, the company's technical staff did not even detect our presence until many hours later. At the time of their official announcement,…”
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with HEC Group (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask HEC Group directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what HEC Group can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: email and communications, employee and hr records.
Within 30 days
- Keep watching HEC Group A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are HEC Group
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: email and communications.
Within 3 days
- Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records.
- Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
- Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 360,000 files. Treat group figures as unverified.
- Check regulatory and stakeholder notification duties No country is recorded for this listing. Identify the data-protection and contractual duties that apply where the affected people live, and ask counsel. General guidance, not legal advice. Why: The listing records no country.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Technology organizations and ask them whether they were affected. Why: dragonforce listed 6 other Technology organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
69/100 • ELEVATEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.