All incidents View linkage analytics →Get the evidence package — $79

Confirmed2 filings · 2 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 2 filings

Vermont State Colleges — May 2020 breach

Clustered 2 filings across 2 jurisdictions · filing window Mar 1, 2021 → Mar 2, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

First → last filing

Mar 1, 2021 → Mar 2, 2021

Merge confidence

100%

incident inc_60ec91794e504608 · merged by deterministic · confidence 100%

Part of the BLACKBAUD, INC. supply-chain incident (2020) — at least 172 organizations filed notifications naming this third party.

Confirmed breach. One breach, 2 legal records. Intrusion May 1, 2020–May 20, 2020, discovered Jul 16, 2020 — the first regulatory filing landed 228 days later. 15 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

228days

Discovered → first regulatory filing

Filing span

1days

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

identity_government

Incident timeline

May 1, 2020breach begins

Jul 16, 2020discovered

notification delay · 228 days

Mar 1, 2021first filing

Mar 2, 2021most recent filing

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

Member cascade — every filing about this breach

MAR 1MA AGMA AG noticefirst filing · 10 MA residentsauto-linkedday 0
MAR 2NH AGNH AG noticemost recent · 5 NH residents+1d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: May 1, 2020 – May 20, 2020
Discovered: Jul 16, 2020· 76d undetected
Data types: Identity (basic) · Government ID · Financial account
Attack vector: Third-Party / Supply Chain
Response: Commenced an investigation to better understand the nature and scope of the incident · Gathered further information from Blackbaud · Provided written notice to potentially affected individuals

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

1 days

vs. multi-state median

5.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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.