DisclosureLens
Leak SiteState AGConfirmed6 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblacksuithigh sensitivity
Merged incident · 6 records

Virginia Farm Bureau Mutual Insurance Company — October 2022 breach

Clustered 6 records across 5 jurisdictions: 5 filings and 1 leak-site claim · filed Feb 15, 2024. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

6 records

States

5

Affected · reported

261,187

First → last filing

Feb 15, 2024

Merge confidence

100%

incident inc_cfdec06557e04810 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. Intrusion Oct 6, 2022–Oct 16, 2022, discovered Oct 1, 2022 — the first regulatory filing landed 502 days later. 261,187 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Financial account, and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
502days

Discovered → first regulatory filing

Discovery variance
326days

Range of discovered_at dates across filings

Leak precedence
426days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
0days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Oct 6, 2022breach begins
Oct 1, 2022discovered · members disagree
notification delay · 502 days
Feb 15, 2024first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing and leak-site claim in this incident

  1. DEC 16Leak siteblacksuit postfirst record · attacker claim · unverifiedday 0
  2. FEB 15IN AGIN AG noticestates nationwide total 261,187+426d
  3. FEB 15MA AGMA AG notice91 MA residents+426d
  4. FEB 15CA AGCA AG noticeno count stated+426d
  5. FEB 15MT AGMT AG notice35 MT residents+426d
  6. FEB 15ME AGME AG noticemost recent · states nationwide total 261,187+426d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 16, 2022
IN AG
Discovered
Oct 1, 2022MT AGOct 6, 2022CA AGAug 23, 2023ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID
MA AG + ME AG + CA AG +1
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)

261,187

Sum of filed state slices

4,605· 1.8% of stated

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

US261,187
ME4,321
IN158
MA91
MT35

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 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 Oct 23, 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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.