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

Service Lighting & Electrical Supplies, Inc. — March 2025 breach

Clustered 12 filings across 11 jurisdictions · filing window Mar 1, 2026 → Mar 9, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

11

Affected · reported

25,736

First → last filing

Mar 1, 2026 → Mar 9, 2026

Merge confidence

100%

incident inc_8aafda3ec87f4e00 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe unauthorized access. Intrusion Mar 12, 2025–Sep 16, 2025, discovered Sep 16, 2025 — the first regulatory filing landed 166 days later (flagged late). 25,736 individuals reported across the linked filings. Data reported: Financial account, PII, PCI, and 2 more. Notifications rolled out on a 8-day schedule across 12 filings beginning Mar 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
166days

Discovered → first regulatory filing

Discovery variance
139days

Range of discovered_at dates across filings

Filing span
8days

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 clocksVermont✗ VT AG >45 bdayOregon✗ OR AG >45dMaine✗ ME AG >90d · 170dWashington✗ WA AG >90dCalifornia✓ CA AG copy ≤15d · 1dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Mar 12, 2025breach begins
Sep 16, 2025discovered · members disagree
notification delay · 166 days
Mar 1, 2026first filing
Mar 9, 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 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAR 4NE AGNE AG noticeno count stated+3d
  3. MAR 4IN AGIN AG noticestates nationwide total 25,736+3d
  4. MAR 4VT AGVT AG noticeno count stated+3d
  5. MAR 4IN AGIN AG noticestates nationwide total 25,736+3d
  6. MAR 5OR AGOR AG noticestates nationwide total 25,736+4d
  7. MAR 5ME AGME AG noticestates nationwide total 25,736+4d
  8. MAR 5CA AGCA AG noticeno count stated+4d
  9. MAR 6WA AGWA AG notice715 WA residents+5d
  10. MAR 6TX AGTX AG noticestates nationwide total 25,736+5d
  11. MAR 6MA AGMA AG noticeno count stated+5d
  12. MAR 9NH AGNH AG noticemost recent · 150 NH residents+8d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 12, 2025 – Sep 16, 2025
NE AG
Discovered
Sep 16, 2025NE AG + VT AG + OR AG +3Feb 2, 2026IL AG + TX AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
IL AG + NE AG + ME AG +6
Attack vector
Unauthorized Access
NE 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)

25,736

Sum of filed state slices

3,174· 12.3% of stated

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

US25,736
TX1,748
WA715
IN410
ME151
NH150

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

8 days

Cadence

~1 / 0.7d

vs. multi-state median

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