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

The Long & Foster Companies, Inc. — August 2020 breach

Clustered 9 filings across 7 jurisdictions · filing window Sep 15, 2020 → Dec 7, 2020. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

85,212

First → last filing

Sep 15, 2020 → Dec 7, 2020

Merge confidence

100%

incident inc_5398733a87f0483f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe a ransomware attack. Intrusion Aug 22, 2020, discovered Aug 22, 2020 — the first regulatory filing landed 24 days later (flagged late). 85,212 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 83-day schedule across 9 filings beginning Sep 15, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
24days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
83days

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 clocksMaine✗ ME AG >90d · 101dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Aug 22, 2020breach begins
Aug 22, 2020discovered
notification delay · 24 days
Sep 15, 2020first filing
Dec 7, 2020most 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. SEP 15MT AGMT AG noticefirst filing · 5 MT residentsday 0
  2. SEP 15IN AGIN AG noticestates nationwide total 85,212day 0
  3. SEP 16ME AGME AG noticestates nationwide total 85,212+1d
  4. SEP 16MA AGMA AG notice101 MA residents+1d
  5. SEP 21NH AGNH AG notice9 NH residents+6d
  6. DEC 1DE AGDE AG noticeno count stated+77d
  7. DEC 1ME AGME AG noticestates nationwide total 9,934+77d
  8. DEC 1CA AGCA AG noticeno count stated+77d
  9. DEC 7NH AGNH AG noticemost recent · 19 NH residents+83d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 22, 2020
MT AG
Discovered
Aug 22, 2020
MT AG + ME AG + NH AG +2
Data types
Employment · Financial · Financial account · Financial credentials · Identity (basic) · Government ID · PII
MT AG + ME AG + NH 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)

85,212

Sum of filed state slices

188· 0.2% of stated

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

US85,212
MA101
IN48
NH19
ME15
MT5

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

83 days

Cadence

~1 / 10.4d

vs. multi-state median

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