DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Merged incident · 2 filings

Penquis — April 2024 breach

Clustered 2 filings across 1 jurisdiction · filing window Jan 15, 2025 → Jan 23, 2025. View entity profile → Other incidents for this victim →

✓ data types agreeMerge86%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

not comparable

First → last filing

Jan 15, 2025 → Jan 23, 2025

Merge confidence

86%

incident inc_0b74c159d9d34218 · merged by deterministic · confidence 86%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filings describe a physical incident. Intrusion Apr 12, 2024, discovered Jan 23, 2025. Data reported: PII. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span
8days

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.

Incident timeline

Apr 12, 2024breach begins
Jan 23, 2025discovered
Jan 15, 2025first filing
Jan 23, 2025most 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. JAN 15ME AGME AG noticefirst filing · 65 affectedday 0
  2. JAN 23ME AGME AG noticemost recent · 20 ME residents+8d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 7, 2024
ME AG
Discovered
Jan 23, 2025· 200d undetected
ME AG
Data types
PII
ME AG

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
0.86 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (86% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

8 days

vs. multi-state median

1.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. 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.