DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed10 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 10 filings

SI Group, Inc. — August 2021 breach

Clustered 10 filings across 6 jurisdictions · filing window Sep 29, 2021 → Jan 11, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

6

Affected · reported

7,241

First → last filing

Sep 29, 2021 → Jan 11, 2022

Merge confidence

100%

incident inc_aba20a9569824c59 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Aug 9, 2021–Aug 14, 2021, discovered Aug 14, 2021 — the first regulatory filing landed 46 days later (flagged late). 7,241 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 2 more. Notifications rolled out on a 104-day schedule across 10 filings beginning Sep 29, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
46days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
104days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine✗ ME AG >90d · 130dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Aug 9, 2021breach begins
Aug 14, 2021discovered
notification delay · 46 days
Sep 29, 2021first filing
Jan 11, 2022most 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. SEP 29IN AGIN AG noticefirst filing · states nationwide total 7,241day 0
  2. SEP 30ME AGME AG noticestates nationwide total 568+1d
  3. OCT 12NH AGNH AG notice1 NH residents+13d
  4. OCT 26MT AGMT AG notice4 MT residents+27d
  5. NOV 3ME AGME AG noticestates nationwide total 3,254+35d
  6. NOV 3MA AGMA AG notice83 MA residents+35d
  7. NOV 12NH AGNH AG notice3 NH residents+44d
  8. DEC 22ME AGME AG noticestates nationwide total 7,241+84d
  9. DEC 29SC AGSC AG notice353 SC residents+91d
  10. JAN 11NH AGNH AG noticemost recent · 9 NH residents+104d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 14, 2021
IN AG
Discovered
Aug 14, 2021
ME AG + MT AG + NH AG +1
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · Minor
ME AG + NH AG + MT AG +2
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)

7,241

Sum of filed state slices

501· 6.9% of stated

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

US7,241
SC353
MA83
IN45
NH9
ME7
MT4

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing10 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 Jun 12, 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

104 days

Cadence

~1 / 11.6d

vs. multi-state median

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