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

IKAV ENERGY INC. — December 2024 breach

Clustered 8 filings across 8 jurisdictions · filing window Mar 12, 2025 → Apr 23, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

5,832

First → last filing

Mar 12, 2025 → Apr 23, 2026

Merge confidence

100%

incident inc_8f5c2340e9ec4f61 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe unauthorized access. Intrusion Dec 6, 2024, discovered Dec 6, 2024 — the first regulatory filing landed 96 days later (flagged late). 5,832 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 407-day schedule across 8 filings beginning Mar 12, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
96days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
407days

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 clocksMaine✗ ME AG >90d · 96dVermont✗ VT AG >45 bdayMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 6, 2024breach begins
Dec 6, 2024discovered
notification delay · 96 days
Mar 12, 2025first filing
Apr 23, 2026most 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 12ME AGME AG noticefirst filing · states nationwide total 5,832day 0
  2. MAR 12MA AGMA AG notice15 MA residentsday 0
  3. MAR 12MT AGMT AG notice36 MT residentsday 0
  4. MAR 12IN AGIN AG noticestates nationwide total 5,832day 0
  5. MAR 12NH AGNH AG noticeno count statedday 0
  6. MAR 12NE AGNE AG noticeno count statedday 0
  7. MAR 12VT AGVT AG noticeno count statedday 0
  8. APR 23MD AGMD AG noticemost recent · 18 MD residents+407d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 6, 2024
ME AG
Discovered
Dec 6, 2024
ME AG + MT AG + NH AG +3
Data types
Identity (basic) · Government ID · PII
ME AG + MT AG + NH AG +3
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)

5,832

Sum of filed state slices

95· 1.6% of stated

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

US5,832
MT36
IN19
MD18
MA15
ME7

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

407 days

Cadence

~1 / 58.1d

vs. multi-state median

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