Clustered 2 filings across 2 jurisdictions · filed Jan 26, 2026. View entity profile → Other incidents for this victim →
incident inc_a3809af89cc14738 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Identity (basic)
NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 9, 2025 → Aug 17, 2025
When the intrusion reportedly occurred, per the linked filings
Aug 17, 2025
Reported by VERMONT AG filing
Melwood, Inc. notified consumers of a data breach occurring between August 9-17, 2025, where an unknown actor accessed its network and copied files containing names and other personal information. Notification was sent on January 26, 2026. Melwood is providing complimentary identity monitoring and evaluating additional technical measures and staff training to prevent recurrence.
Melwood, Inc. notified the New Hampshire Attorney General of a data event affecting approximately 3 New Hampshire residents. Between August 9 and 17, 2025, an unknown cyber actor accessed Melwood's network and copied files containing names and Social Security numbers. Melwood notified federal law enforcement, provided 12 months of complimentary credit monitoring via TransUnion/Cyberscout, and updated internal policies.
Affected (this filing): 3
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.