Leerburg Enterprises, Inc.
bd_0971e1b52710b25b · schema v1 · pii pii-v1
Full breach record for Leerburg Enterprises, Inc. →Leerburg Enterprises, Inc. reported an external system breach (hacking) occurring on September 8, 2020, discovered on January 13, 2022. The incident affected 17,403 individuals, including 98 Maine residents. Acquired data included names and financial account or credit/debit card numbers (with security codes/PINs). Written notification was sent on March 23, 2022. No identity theft protection services were offered.
J jump to incidentP pin to compareR raw source
Incident timeline
Sep 8, 2020
Begins
Jan 13, 2022
Discovered
Mar 23, 2022
Filed
vs. sector median
9 wks faster
Linked disclosures
Why this link?Regulatory filings (8) · sorted by filing gap
- Massachusetts State AGbd_4b4e6b73a196b9b42022-03-23Verified
- Washington State AGbd_78b19265c5f267972022-03-23Verified
- Oregon State AGbd_88bf60d6debe83b32022-03-23Verified
- California State AGbd_93e1458ca41579c02022-03-23Verified
Show 4 more filings ↓Show fewer ↑up to 81d gap
- Montana State AGbd_97536d64f3e26dab2022-03-23Verified
- Indiana State AGbd_c50ad3e42de73d142022-03-23Verified
- New Hampshire State AGbd_054cd912d97744812022-03-28 · +5dVerified
- Illinois State AGbd_429575b9329475072022-01-01 · +81dCandidate
Filing propagation · 9 filings · 9 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Mar 28 (NH) — a 86-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.