Clustered 2 filings across 2 jurisdictions · filing window Mar 26, 2026 → May 14, 2026. View entity profile → Other incidents for this victim →
incident inc_3ddce8c378bd4910 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 23, 2026 → Mar 23, 2026
When the intrusion reportedly occurred, per the linked filings
Mar 23, 2026
Reported by NEW HAMPSHIRE AG filing
Carlysle.net belongs to Carlysle Engineering, Inc., an engineering firm based in Boston. The company specializes in designing, installing, and maintaining fire protection systems such as sprinklers. They also provide building inspections and consulting services to ensure compliance with safety and insurance requirements.
Carlysle Engineering, Inc. notified the New Hampshire Attorney General of a ransomware attack discovered on March 23, 2026. The incident affected approximately 6 New Hampshire residents, exposing employee PII including SSNs and driver's licenses. Carlysle engaged OCD Tech for forensic investigation and containment, updated firewalls, and offered 24 months of identity protection services to affected individuals.
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): 6