DisclosureLens
Leak SiteState AGConfirmed4 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcednitrogenlow sensitivity
Merged incident · 4 filings

F & P Georgia Manufacturing, Inc. — June 2025 breach

Clustered 4 filings across 3 jurisdictions · filing window Aug 6, 2025 Apr 21, 2026. View entity profile → Other incidents for this victim →

affected count agreeMerge100%

Determination

Confirmed

Members

4 filings

States

2

Affected · reported

12,132

First → last filing

Aug 6, 2025 Apr 21, 2026

Merge confidence

100%

incident inc_6eeb603448854043 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings and 1 unverified claim. The filing describes unauthorized access. Intrusion Jun 24, 2025–Jul 2, 2025, discovered Jun 1, 2025 — the first regulatory filing landed 323 days later (flagged late). 12,132 individuals reported across the linked filings. Data reported: PII and Identity (basic). Notifications rolled out on a 257-day schedule across 3 filings beginning Aug 6, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
323days

Discovered → first regulatory filing

Leak precedence
256days 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
257days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delayno SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksMassachusetts MA AG >90dLeak gap Leak >180dFull clock table in Litigation Timeline

Incident timeline

Jun 24, 2025breach begins
Jun 1, 2025discovered
notification delay · 323 days
Apr 20, 2026first filing
Apr 21, 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. AUG 6Leak sitenitrogen postfirst filing · attacker claim · unverifiedday 0
  2. APR 20MA AGMA AG notice1 MA residents+256d
  3. APR 21IN AGIN AG noticestates nationwide total 12,132+257d
  4. APR 21IN AGIN AG noticemost recent · states nationwide total 12,132+257d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 24, 2025Jul 2, 2025
MA AG
Discovered
Jun 1, 2025
MA AG
Data types
Identity (basic) · PII
MA AG
Attack vector
Unauthorized Access
MA 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)

12,132

Sum of filed state slices

23· 0.2% of stated

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

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 filing3 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 11, 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

257 days

Cadence

~1 / 85.7d

vs. multi-state median

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