Confirmed breach. Intrusion Jan 29, 2024–Feb 20, 2024, discovered Feb 20, 2024 — the first regulatory filing landed 59 days later (flagged late). 1,510 individuals reported across the linked filings.
incident inc_c70aa8eddaca4ccc · merge_method human · confidence 100%
Litigation Timing
Notification delay
59days
Discovered → first regulatory filing
Leak precedence
-570days
Gap between first leak claim and first regulatory filing
Filing span
Regulatory clocksOregon✗ OR AG >45dFull clock table in Litigation Timeline
Leak SiteState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedtridentlocker
570days
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Affected (total reported)
1,510
Data types
—
Jurisdictions
2
OR
Linked filings
2
Leak Site · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 29, 2024 → Feb 20, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Feb 20, 2024
Reported by OREGON AG filing
59 days
🦫Oregon State AGFirst filinglinked via shared-victim match · 100%
LMG Holdings Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2024-04-19. The breach occurred during 1/29/2024 - 2/20/2024. The breach was discovered on 2/20/2024. 1,510 individuals were affected. Notice was sent on 4/19/2024.
LMG Holdings, Inc. is a leading provider of ignition interlock devices. Based in Raleigh, North Carolina, the company’s main mission is to provide products that continuously monitor breath alcohol and prevent operation of the vehicle when the driver’s levels are above specified limits. They aim to make the roads safer by preventing drunk driving.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.