SINBON Electronics Co., Ltd
bd_3578d2d64ab46351 · schema v1 · pii pii-v1
Full breach record for SINBON Electronics Co., Ltd →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group DragonForce on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
SINBON Electronics, a leading Taiwanese maker of electronic components that partners with firms such as ASML Holding N.V. and trades under the ticker 3023.TW, posted a notice on the Taiwan Stock Exchange about a cyber-attack on its network. The statement claimed an unknown group carried out the attack, that it was quickly detected and blocked, that a specialized organization would successfully decrypt the files, and that no data were taken. In fact, none of that is accurate. The breach was not anonymous. We always disclose that we performed the intrusion and include our contact information. It’s well known that no one can decrypt what we encrypt without our assistance. Any claim to the contrary has resulted in multi-billion-dollar losses for those who believed it. The incident was not resolved quickly. It unfolded over several weeks and impacted both the headquarters and the U.S. subsidiary. During our operation we exfiltrated a massive volume of company data, including executive-level information. We have now assembled a package of roughly 650,000 files for publication. The collection contains, as usual, financial and accounting records, reports, client data, and personal information. It also includes documentation of the collaboration with ASML Holding N.V., production records, and detailed evidence of product defects and the company’s financial condition. It appears the IT staff tried to conceal the scale of the breach from senior management and regulators to limit personal repercussions. That decision forced us to go public with the incident and its magnitude. We have already sent our contact details to the executives’ email addresses. Please use those details to reach out to us so we can discuss how to keep the data from being released while your company continues to grow and thrive. (The list of files prepared now isn’t final. If needed, we can expand it conside
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 2, 2026
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
dragonforce
According to ransomware.live, DragonForce is a major ransomware-as-a-service operation first observed in August 2023 that launched a formal affiliate program offering 80% revenue share, then rebranded as a "ransomware cartel" in 2025, gaining notoriety for high-profile attacks on UK retailers Marks & Spencer, Co-op, and Harrods.