Clustered 2 filings across 2 jurisdictions · filed Mar 20, 2026. View entity profile → Other incidents for this victim →
incident inc_8ac7be3c9be74469 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · 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.
NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 24, 2025 → Oct 31, 2025
When the intrusion reportedly occurred, per the linked filings
Oct 31, 2025
Reported by VERMONT AG, NEW HAMPSHIRE AG filings
Titan Roofing, Inc. filed a supplemental notice with the Vermont AG regarding a ransomware incident. Unauthorized access occurred on Oct 24, 2025, leading to encryption on Oct 31, 2025. One Vermont resident was notified. Data included names, SSNs, driver's licenses, and financial accounts. Titan engaged law enforcement and offers 24 months of credit monitoring.
Affected (this filing): 1
Titan Roofing, Inc. notified the New Hampshire Attorney General on March 20, 2026, of a ransomware incident affecting one NH resident. Unauthorized access occurred on or about October 24, 2025, and was discovered on October 31, 2025. The incident involved encryption of files and potential access to names, SSNs, driver's license numbers, and financial account information. Titan engaged law enforcement, took systems offline, and provided 24 months of credit monitoring via Experian.
Affected (this filing): 1
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.