DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed16 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedbianlianhigh sensitivity
Merged incident · 16 filings

Carvin Software — February 2023 breach

Clustered 16 filings across 12 jurisdictions · filing window Jan 1, 2023 → Jul 6, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

16 filings

States

11

Affected · reported

356,871

First → last filing

Jan 1, 2023 → Jul 6, 2023

Merge confidence

100%

incident inc_82977a6367724b89 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 15 regulatory filings and 1 unverified claim. Intrusion Feb 22, 2023–Mar 9, 2023, discovered Mar 9, 2023. 356,871 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 186-day schedule across 15 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
43days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 186d

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
186days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 34dWashington⏱ WA AG >30dMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dCalifornia✓ CA 60-day OK · 54dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Feb 22, 2023breach begins
Mar 9, 2023discovered · members disagree
Jan 1, 2023first filing
May 22, 2023most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAY 2ME AGME AG noticestates nationwide total 187,360+121d
  3. MAY 2MT AGMT AG notice2,294 MT residents+121d
  4. MAY 2MA AGMA AG notice10,201 MA residents+121d
  5. MAY 2OR AGOR AG noticestates nationwide total 187,360+121d
  6. MAY 2WA AGWA AG notice9,606 WA residents+121d
  7. MAY 2CA AGCA AG noticeno count stated+121d
  8. MAY 2DE AGDE AG noticeno count stated+121d
  9. MAY 2IN AGIN AG noticestates nationwide total 187,360+121d
  10. MAY 9NH AGNH AG notice2,334 NH residents+128d
  11. MAY 17CA AGCA AG noticeno count stated+136d
  12. MAY 19VT AGVT AG noticeno count stated+138d
  13. MAY 19ME AGME AG noticestates nationwide total 356,871+138d
  14. MAY 19CA AGCA AG noticeno count stated+138d
  15. MAY 22NH AGNH AG notice739 NH residents+141d
  16. JUL 6Leak sitebianlian postmost recent · attacker claim · unverified+186d
  17. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 22, 2023 – Mar 9, 2023
ME AG
Discovered
Mar 9, 2023MT AG + WA AG + CA AG +3Mar 29, 2023ME AG + OR AGApr 21, 2023IL AG + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · Government ID · PII
ME AG + MT AG + WA AG +5
Attack vector
Unauthorized Access
ME 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)

356,871

Sum of filed state slices

44,508· 12.5% of stated

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

US356,871
IN14,394
MA10,201
WA9,606
ME5,679
NH2,334
MT2,294

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 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 Aug 25, 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

186 days

Cadence

~1 / 12.4d

vs. multi-state median

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