DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed13 records · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhublow sensitivity
Merged incident · 13 records

The LoveSac Company — February 2025 breach

Clustered 13 records across 6 jurisdictions: 12 filings and 1 leak-site claim · filing window Sep 4, 2025 → Sep 5, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 records

States

6

Affected · reported

2,299

First → last dated filing

Sep 4, 2025 → Sep 5, 2025

Merge confidence

100%

incident inc_d45eacfab96b41e8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. Intrusion Feb 12, 2025–May 30, 2025, discovered Feb 28, 2025 — the first regulatory filing landed 188 days later (flagged late). 2,299 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
188days

Discovered → first regulatory filing

Discovery variance
91days

Range of discovered_at dates across filings

Leak precedence
182days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
1days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Incident timeline

Feb 12, 2025breach begins
Feb 28, 2025discovered · members disagree
notification delay · 188 days
Sep 4, 2025first dated filing
Sep 5, 2025most recent dated filing

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 and leak-site claim in this incident

  1. FEB 28Leak siteransomhub postfirst record · attacker claim · unverifiedday 0
  2. SEP 4MA AGMA AG notice49 MA residents+188d
  3. SEP 4IN AGIN AG noticestates nationwide total 1,840+188d
  4. SEP 4NE AGNE AG noticefiling day not on record · 12 NE residents—
  5. SEP 4IN AGIN AG noticestates nationwide total 2,299+188d
  6. SEP 4ME AGME AG notice7 ME residents+188d
  7. SEP 4NE AGNE AG noticefiling day not on record · 7 NE residents—
  8. SEP 4NH AGNH AG notice12 NH residents+188d
  9. SEP 4VT AGVT AG noticeno count stated+188d
  10. SEP 4ME AGME AG notice5 ME residents+188d
  11. SEP 4VT AGVT AG noticeno count stated+188d
  12. SEP 5MA AGMA AG notice51 MA residents+189d
  13. SEP 5NH AGNH AG noticemost recent · 6 NH residents+189d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 12, 2025
IN AG
Discovered
Feb 28, 2025NE AG + ME AG + VT AG +1May 30, 2025NE AG + ME AG + NH AGfilings disagree on discovery
Data types
Credentials · Identity (basic)
MA AG + NE AG + ME AG +2
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)

2,299

Sum of filed state slices

124· 5.4% of stated

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

US2,299
MA51
IN42
NE12
NH12
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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 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.

Filing velocity

Spread

1 days

Cadence

~1 / 0.1d

vs. multi-state median

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