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

New Era Enterprises, Inc. — December 2024 breach

Clustered 10 filings across 8 jurisdictions · filing window Feb 11, 2025 → Mar 14, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

8

Affected · reported

1,993

First → last filing

Feb 11, 2025 → Mar 14, 2025

Merge confidence

100%

incident inc_89b4d3f62d1b4d58 · merged by llm · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Dec 9, 2024–Dec 18, 2024, discovered Dec 18, 2024 — the first regulatory filing landed 55 days later (flagged late). 1,993 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 3 more. Notifications rolled out on a 31-day schedule across 10 filings beginning Feb 11, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
55days

Discovered → first regulatory filing

Discovery variance
47days

Range of discovered_at dates across filings

Filing span
31days

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 clocksVermont✗ VT AG >45 bdayWashington⏱ WA AG >30dMaryland⏱ MD AG >30dMaine⏱ ME AG >30d · 42dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 9, 2024breach begins
Dec 18, 2024discovered · members disagree
notification delay · 55 days
Feb 11, 2025first filing
Mar 14, 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. FEB 11WA AGWA AG noticefirst filing · states nationwide total 1,993day 0
  2. FEB 11NH AGNH AG noticeno count statedday 0
  3. FEB 11MD AGMD AG notice285 MD residentsday 0
  4. FEB 11IN AGIN AG notice975 IN residentsday 0
  5. FEB 11ME AGME AG notice16 ME residentsday 0
  6. FEB 12MA AGMA AG notice96 MA residents+1d
  7. MAR 14VT AGVT AG noticeno count stated+31d
  8. MAR 14NH AGNH AG noticeno count stated+31d
  9. MAR 14ME AGME AG notice31 ME residents+31d
  10. MAR 14MT AGMT AG noticemost recent · 9 MT residents+31d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 9, 2024 – Dec 18, 2024
WA AG
Discovered
Dec 18, 2024WA AG + NH AG + MD AG +2Jan 31, 2025ME AGFeb 3, 2025NH AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + MD AG + ME AG +4
Attack vector
Unauthorized Access
WA 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)

1,993

Sum of filed state slices

1,671· 83.8% of stated

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

US1,993
IN975
MD285
WA275
MA96
ME31
MT9

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

31 days

Cadence

~1 / 3.4d

vs. multi-state median

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