FEDERALItem 1.05 · mandatoryMalwareTechnologyInformationIndustrial MachineryRansomwareData EncryptedData ExfiltratedLowActive

Trio-Tech International

bd_9a5efd6faf05d5a9 · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 11, 2026

Filed

Mar 20, 2026

To disclose

9 days

Affected

Not disclosed

Confidence

84%

Full breach record for Trio-Tech International →2 incidents on file

On March 11, 2026, a Singapore-based subsidiary of Trio-Tech International experienced a ransomware incident that encrypted certain files. On March 18, 2026, the incident escalated with unauthorized disclosure of company data, leading management to conclude the event may be material. The subsidiary took its network offline, engaged third-party cybersecurity professionals, notified Singapore law enforcement, and is notifying affected parties. Scope of affected data remains under investigation.

J jump to incidentP pin to compareR raw source

SEC clockMateriality determined Mar 18, 2026 → Filed Mar 20, 20262d ✓ SEC 4-day OK9 days discovery → filing

⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Incident timeline

discovery → filing · 9 days

Mar 11, 2026

Begins

Mar 11, 2026

Discovered

Mar 18, 2026

Scope determined

Mar 20, 2026

Filed

vs. sector median

17 wks faster

Tracked as a single-filing incident — the only disclosure on record for this event so far.ConfirmedView incident

Name: Trio-Tech International
norm: trio tech
SEC CIK: 0000732026
Domain: triotech.com

Name: Trio-Tech International
norm: trio tech
SEC CIK: 0000732026
Domain: triotech.com
Industry: Technologyllm
NAICS 333310 · Commercial and Service Industry Machinery Manufacturing

Discovered: Mar 11, 2026
Breach occurred: Mar 11, 2026
Undetected for: 0 daysoccurrence → discovery
Materiality determined: Mar 18, 2026
Notification sent: —
Affected individuals: Not disclosed
Data types: —
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Notified law enforcement in Singapore

During the incident: Activated its response protocols
Implemented containment measures, including proactively taking its network offline
Launching an investigation with the assistance of third-party cybersecurity professionals
Notifying law enforcement in Singapore
Taking steps to contain the incident, restore affected systems, and enhance monitoring across its network environment
In the process of notifying affected parties as required by applicable law
Working closely with its cyber insurance provider
Changes made: Enhance monitoring across its network environment
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 9 days(9 days from discovery to filing)
Compliance flags: SEC 4-day OK · 2d
Discovery-date grounding: occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
Clock breakdown: Statute Window Elapsed Threshold Status
SEC
Materiality determined: Mar 18, 2026
→ Filed: Mar 20, 2026
2d cal. 4 business days SEC 4-day OK

Statute	Window	Elapsed	Threshold	Status
SEC	Materiality determined: Mar 18, 2026 → Filed: Mar 20, 2026	2d cal.	4 business days	SEC 4-day OK

Status: No extraction artifact recorded for this disclosure.

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statementThis record

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://www.sec.gov/Archives/edgar/data/732026/000143774926009193/trt20260320_8k.htm
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Mar 20, 2026
Raw hash: 9c56457ba6429e0e619eea920b88fed0d74f65a574029c2f4a253d5059976170

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html27.6 KB

Download View at source

Reporting entityTrio-Tech International

Victim entityTrio-Tech International

Incidentdiscovered Mar 11, 2026

Stated responseActivated its response protocols

ComplianceSEC 4-day OK

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing