Trio-Tech International — March 2026 breach
Clustered 2 records across 1 jurisdiction: 1 filing and 1 leak-site claim · filed Mar 20, 2026. View entity profile → Other incidents for this victim →
incident inc_d0a40ab8ac7846d5 · merged by human · confidence 100%
Litigation Timing
Discovered → first regulatory filing
Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.
Discovery to SEC materiality determination
Materiality determination to SEC 8-K filing
Not recorded for this incident
Discovery variance · Filing span — needs two dated filings.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing and leak-site claim in this incident
- MAR 20SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
- APR 8Leak sitegunra postmost recent · attacker claim · unverifiedoperator-confirmed+19d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Mar 11, 2026 SEC 8-K
- Discovered
- Mar 11, 2026 SEC 8-K
- Attack vector
- Ransomware SEC 8-K
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Evidence ladder — rungs this incident occupies
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
No regulator filing linked yet.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Merge provenance
- Method
- human
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Oct 23, 2026 · at least one link edge was human-adjudicated
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.
The weekly clock on records like this one
The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.
Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.