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

First Advantage Corporation — November 2025 breach

Clustered 15 filings across 8 jurisdictions · filing window Apr 21, 2026 → Sep 3, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

15 filings

States

8

Affected · reported

40,596

First → last filing

Apr 21, 2026 → Sep 3, 2026

Merge confidence

100%

incident inc_6d5eb1d186c54d3a · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings. The filings describe a phishing attack. Intrusion Nov 13, 2025–Nov 17, 2025, discovered Nov 17, 2025 — the first regulatory filing landed 155 days later (flagged late). 40,596 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 135-day schedule across 15 filings beginning Apr 21, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
155days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
135days

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 clocksMassachusetts✗ MA AG >90dTexas✗ TX AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 13, 2025breach begins
Nov 17, 2025discovered
notification delay · 155 days
Apr 21, 2026first filing
Sep 3, 2026most 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 21NE AGNE AG noticefirst filing · no count statedday 0
  2. APR 21IN AGIN AG noticestates nationwide total 1,623day 0
  3. APR 21MT AGMT AG notice1 MT residentsday 0
  4. MAY 6MA AGMA AG notice139 MA residents+15d
  5. MAY 29TX AGTX AG noticestates nationwide total 11,369+38d
  6. JUN 4NH AGNH AG notice4 NH residents+44d
  7. JUN 9TX AGTX AG noticestates nationwide total 15,103+49d
  8. JUN 23CA AGCA AG noticeno count stated+63d
  9. JUN 24VT AGVT AG notice4 VT residents+64d
  10. JUN 25TX AGTX AG noticestates nationwide total 31,723+65d
  11. JUN 29NH AGNH AG notice22 NH residents+69d
  12. JUL 23TX AGTX AG noticestates nationwide total 40,596+93d
  13. JUL 27NH AGNH AG notice64 NH residents+97d
  14. JUL 30MA AGMA AG notice75 MA residents+100d
  15. SEP 3TX AGTX AG noticemost recent · 6,272 affected+135d
  16. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 13, 2025
NE AG
Discovered
Nov 17, 2025· 4d undetected
NE AG + MT AG + MA AG +3
Data types
Credentials · Identity (basic) · Government ID · PII
NE AG + MT AG + MA AG +4
Attack vector
Phishing
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)

40,596

Sum of filed state slices

7,682· 18.9% of stated

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

US40,596
TX6,272
IN1,202
MA139
NH64
VT4
MT1

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 filing15 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 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

135 days

Cadence

~1 / 9.6d

vs. multi-state median

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