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

FCDG Management, LLC — October 2023 breach

Clustered 9 filings across 9 jurisdictions · filing window Jul 1, 2024 → Jul 17, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

228,287

First → last filing

Jul 1, 2024 → Jul 17, 2024

Merge confidence

100%

incident inc_853e428a50494149 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe a ransomware attack. Intrusion Oct 22, 2023, discovered Oct 22, 2023 — the first regulatory filing landed 253 days later (flagged late). 228,287 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 4 more. Notifications rolled out on a 16-day schedule across 9 filings beginning Jul 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
253days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
16days

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 · 268dVermont✗ VT AG >45 bdayWashington✗ WA AG >90dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 22, 2023breach begins
Oct 22, 2023discovered
notification delay · 253 days
Jul 1, 2024first filing
Jul 17, 2024most 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. JUL 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUL 16OR AGOR AG noticestates nationwide total 228,287+15d
  3. JUL 16NH AGNH AG notice416 NH residents+15d
  4. JUL 16ME AGME AG noticestates nationwide total 228,287+15d
  5. JUL 16MT AGMT AG notice250 MT residents+15d
  6. JUL 16VT AGVT AG noticeno count stated+15d
  7. JUL 16WA AGWA AG notice1,454 WA residents+15d
  8. JUL 16IN AGIN AG noticestates nationwide total 228,287+15d
  9. JUL 17MA AGMA AG noticemost recent · 1,656 MA residents+16d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 22, 2023
ME AG
Discovered
Oct 22, 2023
IL AG + NH AG + ME AG +3
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
NH AG + ME AG + MT AG +3
Attack vector
Ransomware
NH 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)

228,287

Sum of filed state slices

5,668· 2.5% of stated

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

US228,287
MA1,656
WA1,454
IN1,301
ME591
NH416
MT250

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

16 days

Cadence

~1 / 2d

vs. multi-state median

2.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.