DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed11 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

THE TEAM COMPANIES, LLC — July 2025 breach

Clustered 11 filings across 11 jurisdictions · filing window Nov 1, 2025 → Nov 25, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

21,936

First → last filing

Nov 1, 2025 → Nov 25, 2025

Merge confidence

100%

incident inc_f2f78157d00540a5 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Jul 15, 2025–Jul 26, 2025, discovered Jul 21, 2025 — the first regulatory filing landed 103 days later (flagged late). 21,936 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 4 more. Notifications rolled out on a 24-day schedule across 11 filings beginning Nov 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
103days

Discovered → first regulatory filing

Discovery variance
93days

Range of discovered_at dates across filings

Filing span
24days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon✗ OR AG >45dMaine✓ ME AG ≤30d · 30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 15, 2025breach begins
Jul 21, 2025discovered · members disagree
notification delay · 103 days
Nov 1, 2025first filing
Nov 25, 2025most 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. NOV 1IL AGIL AG noticefirst filing · no count statedday 0
  2. NOV 21CA AGCA AG noticeno count stated+20d
  3. NOV 21OR AGOR AG noticestates nationwide total 21,936+20d
  4. NOV 21NE AGNE AG noticeno count stated+20d
  5. NOV 21MT AGMT AG notice18 MT residents+20d
  6. NOV 21RI AGRI AG notice296 RI residents+20d
  7. NOV 21IN AGIN AG noticestates nationwide total 21,936+20d
  8. NOV 21NH AGNH AG notice23 NH residents+20d
  9. NOV 21ME AGME AG noticestates nationwide total 21,936+20d
  10. NOV 21MA AGMA AG notice324 MA residents+20d
  11. NOV 25TX AGTX AG noticemost recent · states nationwide total 21,936+24d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 15, 2025 – Jul 26, 2025
CA AG
Discovered
Jul 21, 2025OR AG + NE AG + MT AG +2Oct 22, 2025IL AG + ME AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
IL AG + NE AG + MT AG +6
Attack vector
Unauthorized Access
NE 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)

21,936

Sum of filed state slices

2,266· 10.3% of stated

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

US21,936
TX1,549
MA324
RI296
IN30
ME26
NH23
MT18

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 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 Jun 12, 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

24 days

Cadence

~1 / 2.4d

vs. multi-state median

3.0× 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.