All incidents View linkage analytics →Get the evidence package — $7.99 what’s inside →

Confirmed4 filings · 1 stateUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 4 filings

The Village Bank — July 2024 breach

Clustered 4 filings across 1 jurisdiction · filing window May 19, 2026 → Jul 22, 2026. View entity profile → Other incidents for this victim →

✓ data types agreeMerge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

not comparable

First → last filing

May 19, 2026 → Jul 22, 2026

Merge confidence

100%

incident inc_02f88218a1044b1d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe a third-party compromise. Intrusion Jul 1, 2024–Jun 30, 2026. Data reported: Authentication, Financial account, and PCI. Notifications rolled out on a 64-day schedule across 4 filings beginning May 19, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span

64days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Sensitive data

authentication

Incident timeline

Jul 1, 2024breach begins

May 19, 2026first filing

Jul 22, 2026most recent filing

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing about this breach

MAY 19MA AGMA AG noticefirst filing · 2 MA residentsday 0
JUN 10MA AGMA AG notice5 MA residents+22d
JUN 11MA AGMA AG notice1 MA residents+23d
JUL 22MA AGMA AG noticemost recent · 2 MA residents+64d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Oct 3, 2025 – May 4, 2026
Discovered: —
Data types: Authentication · Financial account · PCI
Attack vector: Third-Party / Supply Chain

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

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

64 days

Cadence

~1 / 21.3d

vs. multi-state median

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