Clustered 2 filings across 2 jurisdictions · filed Feb 6, 2026. View entity profile → Other incidents for this victim →
incident inc_878d447f2af6417e · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PII · Government ID · Financial account
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.
ME NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 1, 2025
When the intrusion reportedly occurred, per the linked filings
Dec 1, 2025
Reported by NEW HAMPSHIRE AG, MAINE AG filings
Haley’s Metal Shop, Inc. notified the New Hampshire Attorney General of a phishing incident on December 1, 2025, involving one employee's email account. The breach exposed the name and Social Security number of one New Hampshire resident. The company mailed a notification letter on February 6, 2026, and provided 12 months of complimentary credit monitoring.
Affected (this filing): 1
On December 1, 2025, Haley's Metal Shop, Inc. (Biddeford, ME) identified an email phishing incident in which an unauthorized actor accessed one employee's email account. Review of the account completed January 23, 2026 confirmed that emails contained name, Social Security number, driver's license number, and/or financial account information of 54 Maine residents (57 total). Notifications mailed February 6, 2026; one year of Epiq Privacy ID Solutions credit monitoring offered at no cost.
Affected (this filing): 54
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.