DisclosureLens
State AGConfirmed3 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 3 filings

Newcourse Communications — April 2022 breach

Clustered 3 filings across 3 jurisdictions · filing window Mar 9, 2023 Mar 14, 2023. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

8,373

First → last filing

Mar 9, 2023 Mar 14, 2023

Merge confidence

100%

incident inc_e9ee8d532e754863 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe unauthorized access. Intrusion Apr 27, 2022–May 3, 2022, discovered Feb 15, 2023 — the first regulatory filing landed 22 days later. 8,373 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, and Financial credentials. Notifications rolled out on a 5-day schedule across 3 filings beginning Mar 9, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
22days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
5days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine ME AG ≤30d · 27dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Apr 27, 2022breach begins
Feb 15, 2023discovered
notification delay · 22 days
Mar 9, 2023first filing
Mar 14, 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. MAR 9MT AGMT AG noticefirst filing · 1 MT residentsday 0
  2. MAR 14MA AGMA AG notice6 MA residents+5d
  3. MAR 14ME AGME AG noticemost recent · states nationwide total 8,373+5d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 27, 2022May 3, 2022
MT AG
Discovered
Feb 15, 2023· 294d undetected
MT AG + ME AG
Data types
Financial account · Financial credentials · Identity (basic)
MT AG + ME AG + MA AG
Attack vector
Unauthorized Access
MT 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)

8,373

Sum of filed state slices

8· 0.1% of stated

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

US8,373
MA6
MT1
ME1

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

5 days

Cadence

~1 / 2.5d

vs. multi-state median

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