Better tools. Better news.
Sunday, November 22, 2026 · UTC
Tech

Thomson Reuters Detects Cybersecurity Incident Accessing C-Track Files

Thomson Reuters confirmed an unauthorized party accessed C-Track case management files in multiple US states and Canada.

TruthFoundry News Desk
References:
Updated
Share on X
Stands on 10 placed sources from 3 publishers.
Thomson Reuters detected a cybersecurity incident on June 30 involving its C-Track case management platform across 11 US states, the US Virgin Islands, and Canada. [1] Thomson Reuters stated that an unauthorized party obtained certain C-Track files in March. [2] The unauthorized intrusion exposed court records and personal information across 11 US states, the US Virgin Islands, and Ontario, Canada. [3] Thomson Reuters confirmed on June 30, 2026, that a cyberattack occurred in March 2026 targeting its C-Track court management system. [4] The compromised files included names and personal information of individuals involved in court proceedings or mentioned in court documents. [5] The incident affected court systems in Alabama, Pennsylvania, Kentucky, Montana, Nevada, North Dakota, South Carolina, Tennessee, Ohio, New Hampshire, Wyoming, and the U.S. Virgin Islands. [6] A Thomson Reuters spokesperson said on June 30, 2026, that there has been no operational disruption to C-Track as a result of the incident. [7] West Publishing said it discovered the unauthorized activity on June 30, 2026, affecting courts in 11 U.S. states, the U.S. Virgin Islands, and Ontario, Canada. [8] West Publishing stated that a subset of court records could contain individuals' names, Social Security numbers, driver's license numbers, dates of birth, medical information, and health insurance information. [9] The Hacker News reviewed the West Publishing notice on September 3, 2026, noting it lists 24 court bodies in 11 states and the U.S. Virgin Islands, with Minnesota absent from the list. [10]
Proof10 sources · 3 publishers
What this stands on
  1. Thomson Reuters detected a cybersecurity incident on June 30 involving its C-Track case management platform across 11 US states, the US Virgin Islands, and Canada. · Investing.com
  2. Thomson Reuters stated that an unauthorized party obtained certain C-Track files in March. · Investing.com
  3. The unauthorized intrusion exposed court records and personal information across 11 US states, the US Virgin Islands, and Ontario, Canada. · TechRadar
  4. Thomson Reuters confirmed on June 30, 2026, that a cyberattack occurred in March 2026 targeting its C-Track court management system. · TechRadar
  5. The compromised files included names and personal information of individuals involved in court proceedings or mentioned in court documents. · Investing.com
  6. The incident affected court systems in Alabama, Pennsylvania, Kentucky, Montana, Nevada, North Dakota, South Carolina, Tennessee, Ohio, New Hampshire, Wyoming, and the U.S. Virgin Islands. · Investing.com
  7. A Thomson Reuters spokesperson said on June 30, 2026, that there has been no operational disruption to C-Track as a result of the incident. · TechRadar
  8. West Publishing said it discovered the unauthorized activity on June 30, 2026, affecting courts in 11 U.S. states, the U.S. Virgin Islands, and Ontario, Canada. · The Hacker News
  9. West Publishing stated that a subset of court records could contain individuals' names, Social Security numbers, driver's license numbers, dates of birth, medical information, and health insurance information. · The Hacker News
  10. The Hacker News reviewed the West Publishing notice on September 3, 2026, noting it lists 24 court bodies in 11 states and the U.S. Virgin Islands, with Minnesota absent from the list. · The Hacker News
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · 10 sources · v 002The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Thursday, September 3, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world3 publishers reported the events across 3 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)ba571ea4bfd82a94352dd5be83f424b7c33cae7a16fbe5c7e601fe149aa5602d
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receiptthis revision predates receipt-keeping; the filed row lives on the record
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.