MalwareRansomwareData EncryptedTargetedIDENTITY_BASICIDENTITY_GOVERNMENTMediumContained
Natare
bd_ac46b7cec1805f9d · schema v1 · pii pii-v1
Full breach record for Natare →Natare Corporation, a swimming pool equipment manufacturer, reported a ransomware event on August 13, 2025, resulting in server encryption. The unauthorized actor had access for less than three hours. One New Hampshire resident's name and SSN were acquired. Notifications were mailed October 6, 2025, offering 12 months of credit monitoring. Remediation included MFA, password resets, and enhanced monitoring.
Leak gap clock⏱ Leak >30d8 weeks discovery → filing
⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
This filing is one of 2 about the same incident.View merged incident
A leak claim by akira about this victim predates this filing by 38 days.View originating leak claim
Linked disclosures
Why this link?Regulatory filings (1) · sorted by filing gap
- bd_0f697bfeaaf3a83eIndiana State AGfiled 2025-10-06(4d gap)Candidate
Source provenance
- Source URL
- https://mm.nh.gov/files/uploads/doj/remote-docs/natare-20251010.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Oct 10, 2025
- Raw hash
- a5b93eec450ee25404ae46d8d2a8ddab8dcd8a4ed706c134e58e4b3d41149dcc
Reporting entity
- Name
- Kennedys CMK LLPnorm: kennedys cmk
Victim entity
- Name
- Natarenorm: natare
- Domain
- natare.com
Incident
- Discovered
- Aug 13, 2025
- Materiality determined
- —
- Notification sent
- Oct 6, 2025
- Affected individuals
- 1
- Data types
- IDENTITY_BASICIDENTITY_GOVERNMENT
- Attack vector
- Ransomware
- MITRE ATT&CK
- T1486 Data Encrypted for ImpactT1078 Valid Accounts
- Threat actor
- ExternalFinancial
- Regulator citations
- Notified New Hampshire Attorney GeneralReported the incident to federal law enforcement
Compliance
- Time to disclose
- 8 weeks(58 days from discovery to filing)
- Compliance flags
- Leak >30d
- Discovery-date grounding
- occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.