DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed9 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcontihigh sensitivity
Merged incident · 9 filings

TIC International Corporation — March 2022 breach

Clustered 9 filings across 8 jurisdictions · filing window Apr 12, 2022 → Nov 2, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

187,341

First → last filing

Apr 12, 2022 → Nov 2, 2022

Merge confidence

100%

incident inc_2c2a3adab2af4fba · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. Intrusion Mar 25, 2022–Mar 30, 2022, discovered Mar 30, 2022 — the first regulatory filing landed 160 days later (flagged late). 187,341 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 4 more. Notifications rolled out on a 204-day schedule across 8 filings beginning Apr 12, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
160days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
147days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
204days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dOregon✗ OR AG >45dMaine✗ ME AG >90d · 163dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Mar 25, 2022breach begins
Mar 30, 2022discovered
notification delay · 160 days
Sep 6, 2022first filing
Nov 2, 2022most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. APR 12Leak siteconti postfirst filing · attacker claim · unverifiedday 0
  2. SEP 6IN AGIN AG noticestates nationwide total 187,341+147d
  3. SEP 9MT AGMT AG notice82 MT residents+150d
  4. SEP 9OR AGOR AG noticestates nationwide total 187,341+150d
  5. SEP 9ME AGME AG noticestates nationwide total 187,341+150d
  6. SEP 10MA AGMA AG notice1,030 MA residents+151d
  7. SEP 15NH AGNH AG notice42 NH residents+156d
  8. NOV 1HHS OCRHHS OCR noticestates nationwide total 1,362+203d
  9. NOV 2CA AGCA AG noticemost recent · no count stated+204d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 25, 2022
IN AG
Discovered
Mar 30, 2022· 5d undetected
MT AG + OR AG + ME AG +1
Data types
Employment · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PII
MT AG + CA AG + ME AG +3
Attack vector
Ransomware
MT AG

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)

187,341

Sum of filed state slices

18,539· 9.9% of stated

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

US187,341
IN17,323
MA1,030
MT82
ME62
NH42

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 report

No press coverage linked yet.

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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 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

204 days

Cadence

~1 / 25.5d

vs. multi-state median

25.5× slower

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.