DisclosureLens
Leak SiteState AGConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedqilin
Merged incident · 2 filings

North Platte Natural Resources District — November 2024 breach

Clustered 2 filings across 2 jurisdictions · filing window Nov 27, 2024 Nov 29, 2024. View entity profile → Other incidents for this victim →

Agreement not assessableMerge100%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

First → last filing

Nov 27, 2024 Nov 29, 2024

Merge confidence

100%

incident inc_bf967b8a0bf24955 · merged by deterministic · confidence 100%

Confirmed breach. Intrusion Nov 27, 2024, discovered Nov 29, 2024.

Litigation Timing

Notification delay
0days

Discovered → first regulatory filing

Leak precedence
2days before filing

Days between the first leak-site claim and the first regulatory filing. 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
2days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delayno SEC 8-K in this cluster; needs two dated filings.

Incident timeline

Nov 27, 2024breach begins
Nov 29, 2024discovered
notification delay · 0 days
Nov 29, 2024first & only filing
watching for filings

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

Member cascade — every filing about this breach

  1. NOV 27Leak siteqilin postfirst filing · attacker claim · unverifiedday 0
  2. NOV 29NE AGNE AG noticemost recent · no count stated+2d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 27, 2024
NE AG
Discovered
Nov 29, 2024· 2d undetected
NE 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 claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing1 member

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

2 days

vs. multi-state median

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