Lindahl Brothers Inc — August 2024 breach

Clustered 2 filings across 2 jurisdictions · filed Dec 20, 2024 (dated filings only). View entity profile → Other incidents for this victim →

✓ affected count agreeMerge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

740

First → last dated filing

Dec 20, 2024

Merge confidence

100%

incident inc_98f42f1c111c4fc4 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. Intrusion Aug 11, 2024, discovered Aug 11, 2024. 740 individuals reported across the linked filings. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Incident timeline

Aug 11, 2024breach begins

Aug 11, 2024discovered

Dec 20, 2024first dated filing

—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

DEC 1IL AGIL AG noticefiling day not on record · no count statedoperator-confirmed—
DEC 20IN AGIN AG noticefirst filing · states nationwide total 740day 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Aug 11, 2024
Discovered: Aug 11, 2024

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)

740

Sum of filed state slices

57· 7.7% of stated

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

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: human
Confidence: 1.00 · above the 0.85 auto-merge floor
Reviewed: operator-reviewed Oct 23, 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.

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.