All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed10 records · 8 statesUnverified claimConfirmedEnforcedblacksuithigh sensitivity

Merged incident · 10 records

TRC Talent Solutions — March 2024 breach

Clustered 10 records across 8 jurisdictions: 8 filings, 1 press report and 1 leak-site claim · filing window May 24, 2024 → May 28, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 records

States

Affected · reported

158,593

First → last dated filing

May 24, 2024 → May 28, 2024

Merge confidence

100%

incident inc_1fbcb4fd4d3649d7 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings, 1 press report and 1 unverified claim. Intrusion Mar 25, 2024–Apr 12, 2024, discovered Mar 25, 2024. 158,593 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Discovery variance

45days

Range of discovered_at dates across filings

Filing span

4days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksWashington⏱ WA AG >30dVermont⏱ VT AG >14 bdayMaine✓ ME AG ≤30d · 15dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 25, 2024breach begins

Mar 25, 2024discovered · members disagree

May 24, 2024first dated filing

May 28, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

APR 12Leak siteblacksuit postfirst record · attacker claim · unverifiedoperator-confirmedday 0
MAY 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
MAY 24WA AGWA AG notice2,792 WA residentsoperator-confirmed+42d
MAY 24ME AGME AG noticestates nationwide total 158,593operator-confirmed+42d
MAY 24MT AGMT AG notice2 MT residentsoperator-confirmed+42d
MAY 24VT AGVT AG noticeno count statedoperator-confirmed+42d
MAY 24IN AGIN AG noticestates nationwide total 158,593operator-confirmed+42d
MAY 24MA AGMA AG notice640 MA residentsoperator-confirmed+42d
MAY 28SC AGSC AG noticemost recent · 8,880 SC residentsauto-linked+46d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 25, 2024 – Apr 12, 2024
Discovered: Mar 25, 2024IL AGApr 12, 2024WA AG + MT AG + VT AG +1May 9, 2024ME AGfilings disagree on discovery
Data types: Identity (basic) · Government ID
Attack vector: Ransomware

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

158,593

Sum of filed state slices

12,406· 7.8% of stated

92% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US158,593

SC8,880

WA2,792

MA640

IN86

ME6

MT2

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

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

Press / market report1 member

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

State AG / regulator filing8 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method: human
Confidence: 1.00 · above the 0.85 auto-merge floor
Reviewed: operator-reviewed Aug 25, 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.

Filing velocity

Spread

4 days

Cadence

~1 / 0.7d

vs. multi-state median

1.5× faster

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.