Incident · 8-K Item 1.05
Radiant Logistics isolates its Canadian operations after detecting an intrusion
Compiled from public records. Updated 2026-11-08. By the cisonews.net Desk.
Radiant Logistics, Inc. disclosed to the SEC on March 20, 2024, under Item 1.05 of Form 8-K, that it had detected the initial stages of a cybersecurity incident tied to its Canadian operations on or about March 14, 2024. The filing names no category of personal or business information and gives no count of affected people.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
What happened and when
The company says its information technology monitoring tools picked up the activity. The filing lists the date of the earliest event reported as March 19, 2024, while the detection date it describes is on or about March 14, 2024.
Radiant states it responded at once by starting its response and continuity plans. It also cut the Canadian business off from the rest of its network as a precaution. Outside cybersecurity and forensics professionals were hired to assess, contain and remediate the incident.
Effect on customers and operations
Customers in Canada experienced delays, according to the filing, and recovery work was under way when it was made. The company expected that work to be mostly finished within about a week of the filing. Operations in the United States and in other international markets are described as running normally in all material respects.
Financial statement
Radiant says the investigation was still going on and that the incident had not materially affected overall operations. It also says it had not concluded that a material effect on its financial condition or results was reasonably likely.
The forward-looking section adds caution. Management believed early findings suggested its defensive measures may have limited the scope, with no assurance of that. The company also said it could not be certain disruption would stay within Canada.
How did Radiant's investigation end?
Radiant's quarterly report filed on November 12, 2024 says the investigation is complete. It found the incident did not materially affect the company's operations, financial condition or results. The same report describes the response. Radiant isolated its Canadian operations from the rest of its network and brought in cybersecurity and forensics firms. Customers in Canada saw service delays, and systems recovery was completed promptly. Its U.S. and other international operations ran without material disruption throughout.
The annual report for the year ended June 30, 2024 adds that the incident led to a modest loss of revenue and some extra costs. That passage sits beside a December 8, 2021 ransomware incident, and says that in both cases Radiant recovered its systems and returned to full operation. It gives no amount, and the wording does not make clear which of the two incidents the revenue loss refers to.
| Date | What Radiant reported |
|---|---|
| March 14, 2024 | Early stages of an incident detected in Canadian operations |
| March 20, 2024 | 8-K under Item 1.05 |
| September 12, 2024 | 10-K: systems recovered; modest revenue loss and incremental costs |
| November 12, 2024 | 10-Q: investigation complete; no material impact on operations or finances |
| September 15, 2025 | 10-K: Canadian systems back in service within one week; security program enhanced |
Radiant's annual report for the year ended June 30, 2025 tells the March 2024 attack in more operational detail than the earlier filings. The attack was caught by the company's endpoint protection software and its third-party monitoring partner. Radiant then shut down its Canadian infrastructure, and the systems were restored and cleared to return to service within one week. It has since added tools and stronger system and network monitoring, and it says it does not expect further material harm from either this attack or the December 2021 one. The 2021 attack, by contrast, disrupted operations for about two weeks.
Item 8.01 versus Item 1.05 explains when an incident is filed under one item or the other.
What the documents leave open
The filing does not say what type of attack occurred, whether any data was taken, or which Canadian systems were affected. It does not say whether a ransom was demanded, though it mentions the possibility that the company might pay one. No 8-K amendment is on record. The later reports above give the end of the investigation and the recovery, but not whether data was taken or whether anyone was notified.
How this disclosure's timing compares
Radiant Logistics disclosed 6 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 transportation & logistics incidents on cisonews.net
- Uber Technologies, Inc., Breach notice, first disclosed November 10, 2026
- Caltrain, Breach notice, first disclosed November 3, 2026
- STS Aviation Group, Breach notice, first disclosed October 19, 2026; 54,027 affected in total (Indiana Attorney General)
- Preferred Parking Service, LLC, Breach notice, first disclosed August 14, 2026; affected: 72,912 people in total (Indiana AG record)
- Yellow Corporation, Breach notice, first disclosed June 26, 2026; affected: 258,498 people (Oregon DOJ record)
Guides for this kind of filing
Sources
- 2024-03-20 · ARadiant Logistics, Inc., Form 8-K (SEC EDGAR), published March 20, 2024
- 2024-09-12 · ARadiant Logistics, Form 10-K for the period ended 2024-06-30 (SEC EDGAR), published September 12, 2024
- 2024-11-12 · ARadiant Logistics, Form 10-Q for the period ended 2024-09-30 (SEC EDGAR), published November 12, 2024
- 2025-09-15 · ARadiant Logistics, Inc., Form 10-K for the year ended June 30, 2025 (SEC EDGAR), published September 15, 2025
- 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.