GLOBALClaimed by HiveFirst sighting
Posted to leak site Jul 14, 2022bd_470914cee51c965b
Clustered 3 filings across 3 jurisdictions · filing window Jul 14, 2022 → Sep 13, 2022. View entity profile → Other incidents for this victim →
incident inc_6363e625feac437f · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
ME NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 14, 2021 → Jun 12, 2022
When the intrusion reportedly occurred, per the linked filings
Jun 12, 2022
Reported by NEW HAMPSHIRE AG filing
Aug 19, 2022
Reported by MAINE AG filing
City Furniture, Inc. notified the New Hampshire Attorney General of a cybersecurity incident involving unauthorized access to its network between November 14, 2021, and June 12, 2022. The breach affected the personal information, including names and Social Security numbers, of two New Hampshire residents. City Furniture discovered the suspicious activity on June 12, 2022, engaged third-party forensic investigators, and notified law enforcement. Notifications were mailed to affected individuals on September 13, 2022, offering credit monitoring services.
City Furniture, Inc. reported an external system breach (hacking) occurring between November 14, 2021, and June 12, 2022, discovered on August 19, 2022. The incident compromised the names and Social Security Numbers of 7,690 individuals, including 1 Maine resident. City Furniture notified consumers in writing on September 13, 2022, and provided one year of credit monitoring and identity theft protection services through IDX.
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.
Affected (this filing): 7,690