Incident · 8-K Item 1.05
Trio-Tech International reports ransomware at a Singapore subsidiary that escalated to data disclosure
Compiled from public records. Updated 2026-11-07. By the cisonews.net Desk.
Trio-Tech International filed an Item 1.05 Form 8-K with the SEC on March 20, 2026, reporting a ransomware incident at one of its Singapore subsidiaries that was identified on March 11, 2026 and later led to unauthorized disclosure of company data. The filing does not say what kinds of data were involved or how many people are affected.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
What happened and when
The company says it identified and responded to the incident on March 11, 2026. The ransomware encrypted certain files within the company's network. At that stage management judged the matter not material.
Seven days later the situation changed. After the March 18 data disclosure, management revised its view and concluded the event may be material. The report was signed two days after that, on March 20, 2026.
Response described in the filing
The subsidiary took its network offline as a containment step and began an investigation with outside cybersecurity professionals. Work is continuing to contain the incident, restore systems and increase monitoring.
Notification of affected parties is under way, according to the company. The subsidiary is also working with its cyber insurance provider on the investigation, remediation and a possible claims process.
Effect on operations and finances
Trio-Tech reports no material disruption so far and does not expect a material effect on results for the three months ended March 31, 2026. It cautions that the picture could change.
What Trio-Tech's 10-Q and 10-K add
Trio-Tech's next two reports describe the attack more fully than the 8-K. The 10-Q for the quarter ended March 31, 2026, filed on May 14, says the ransomware encrypted certain files on the Singapore subsidiary's network. It adds that the subsidiary told law enforcement in Singapore and that the company did not then expect a material financial impact.
The annual report for the year ended June 30, 2026, filed on September 24, closes several of the open points. It says the company rebuilt the affected systems and strengthened monitoring and security controls across its network. It says no new unauthorized activity has been seen since containment began. It also reports that the law enforcement authorities finished their review and will take no further action against the company. Trio-Tech holds cybersecurity insurance that could offset costs and losses from the incident, including those tied to the data, litigation and regulatory actions.
| Date | What happened | Filing |
|---|---|---|
| March 11, 2026 | Ransomware found at the Singapore subsidiary; network taken offline | 8-K, 10-Q, 10-K |
| March 18, 2026 | Incident escalated to unauthorized disclosure of company data | 8-K, 10-K |
| March 20, 2026 | Item 1.05 Form 8-K filed | 8-K |
| May 14, 2026 | 10-Q: no material financial impact expected | 10-Q |
| September 24, 2026 | 10-K: systems rebuilt; law enforcement review closed with no further action | 10-K |
Which part of Trio-Tech was hit?
One of its subsidiaries in Singapore, according to the 8-K, the 10-Q and the 10-K.
Was data stolen?
The company says the incident escalated on March 18, 2026 and resulted in the unauthorized disclosure of certain company data. None of the filings says what the data was.
Is the incident over?
The 10-K says the affected systems were rebuilt and no new unauthorized activity has been seen, and that the Singapore authorities closed their review.
What the filings leave open
None of the filings names the categories of data disclosed, says where or how the data was disclosed, states a number of affected individuals, or describes any ransom demand. It also gives no letter, call-center number or enrollment deadline for affected parties.
How this disclosure's timing compares
Trio-Tech International disclosed 9 days after the discovery date its filing gives. Across the 46 other filings under 8-K Item 1.05 on cisonews.net that date discovery to the day, the median gap is 6 days.
The rule behind an Item 1.05 filing
Form 8-K Item 1.05 is where a public company reports a cybersecurity incident it has determined to be material. Under the rule the SEC adopted on July 26, 2023, the filing is generally due four business days after the company determines that the incident is material. Source: U.S. Securities and Exchange Commission, press release 2023-139. The guide What is SEC Form 8-K Item 1.05, and what counts as a disclosed cyber incident? reads the rule in full, and the glossary defines Form 8-K Item 1.05.
Other technology incidents on cisonews.net
- DreamHost, Breach notice, first disclosed November 2, 2026
- Photon Health, Breach notice, first disclosed October 28, 2026; affected: approximately 1706 Rhode Island residents
- Indico Data Solutions, Breach notice, first disclosed October 27, 2026; affected: 79 Rhode Island residents
- Stitch Connect Inc, Breach notice, first disclosed September 21, 2026; affected: 113,727 people in total (Indiana AG record)
- IDScan.net, Breach notice, first disclosed September 18, 2026; 27,624 affected in total (Indiana Attorney General)
Sources
- 2026-03-20 · ATrio-Tech International, Form 8-K (SEC EDGAR), published March 20, 2026
- 2026-05-14 · ATrio-Tech International, Form 10-Q for the quarter ended March 31, 2026 (SEC EDGAR), published May 14, 2026
- 2026-09-24 · ATrio-Tech International, Form 10-K for the fiscal year ended June 30, 2026 (SEC EDGAR), published September 24, 2026
- 2023-07-26 · AU.S. Securities and Exchange Commission, press release 2023-139, published July 26, 2023
Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.