DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed7 records · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedqilinhigh sensitivity
Merged incident · 7 records

Upper Merion Township — December 2023 breach

Clustered 7 records across 6 jurisdictions: 6 filings and 1 leak-site claim · filing window Sep 25, 2024 → Oct 16, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 records

States

6

Affected · reported

2,961

First → last filing

Sep 25, 2024 → Oct 16, 2024

Merge confidence

100%

incident inc_0536f3feec754eb0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe malware. Intrusion Dec 24, 2023–Dec 27, 2023, discovered Dec 27, 2023 — the first regulatory filing landed 273 days later (flagged late). 2,961 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 21-day schedule across 6 filings beginning Sep 25, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
273days

Discovered → first regulatory filing

Discovery variance
226days

Range of discovered_at dates across filings

Leak precedence
228days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
21days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 24, 2023breach begins
Dec 27, 2023discovered · members disagree
notification delay · 273 days
Sep 25, 2024first filing
Oct 16, 2024most recent filing

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

Member cascade — every filing and leak-site claim in this incident

  1. JAN 15Leak siteqilin postfirst record · attacker claim · unverifiedday 0
  2. SEP 25IN AGIN AG noticestates nationwide total 2,961+254d
  3. SEP 25VT AGVT AG noticeno count stated+254d
  4. SEP 25ME AGME AG noticestates nationwide total 2,961+254d
  5. SEP 25MT AGMT AG notice3 MT residents+254d
  6. SEP 30NH AGNH AG notice2 NH residents+259d
  7. OCT 16MA AGMA AG noticemost recent · 15 MA residents+275d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 24, 2023
IN AG
Discovered
Dec 27, 2023VT AG + MT AG + NH AGAug 9, 2024ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
VT AG + ME 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)

2,961

Sum of filed state slices

27· 0.9% of stated

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

US2,961
MA15
IN6
MT3
NH2
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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing6 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 22, 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

21 days

Cadence

~1 / 4.2d

vs. multi-state median

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