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

CALTON & ASSOCIATES, INC. — March 2025 breach

Clustered 9 filings across 8 jurisdictions · filing window Apr 13, 2025 → Jul 29, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

1,320

First → last filing

Apr 13, 2025 → Jul 29, 2025

Merge confidence

100%

incident inc_47a01d34ed814994 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. Intrusion Mar 28, 2025–Jun 20, 2025, discovered Mar 28, 2025 — the first regulatory filing landed 90 days later (flagged late). 1,320 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 106-day schedule across 8 filings beginning Apr 13, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
90days

Discovered → first regulatory filing

Discovery variance
1days

Range of discovered_at dates across filings

Leak precedence
73days 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
106days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon✗ OR AG >45dLeak gap⏱ Leak >30dWashington⏱ WA AG >30dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Mar 28, 2025breach begins
Mar 28, 2025discovered · members disagree
notification delay · 90 days
Jun 26, 2025first filing
Jul 29, 2025most 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. APR 13Leak sitecl0p postfirst filing · attacker claim · unverifiedday 0
  2. JUN 26CA AGCA AG noticeno count stated+73d
  3. JUN 26MA AGMA AG notice168 MA residents+73d
  4. JUN 26NE AGNE AG notice273 NE residents+73d
  5. JUN 26MT AGMT AG notice217 MT residents+73d
  6. JUN 26WA AGWA AG notice662 WA residents+73d
  7. JUN 30OR AGOR AG noticestates nationwide total 926+77d
  8. JUL 1IL AGIL AG noticeno count stated+78d
  9. JUL 29MA AGMA AG noticemost recent · 168 MA residents+106d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 28, 2025
CA AG
Discovered
Mar 28, 2025NE AG + MT AG + WA AG +1Mar 29, 2025IL AGfilings disagree on discovery
Data types
Authentication · Financial account · Identity (basic) · Government ID · PII
CA AG + NE AG + MT AG +3
Attack vector
Unauthorized Access
CA AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

US926
WA662
NE273
MT217
MA168

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

106 days

Cadence

~1 / 13.3d

vs. multi-state median

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