HackingTargetedIDENTITY_BASICLowContained
Erving Industries, Inc.
bd_ebff1fa2719ec2f1 · schema v1 · pii pii-v1
Full breach record for Erving Industries, Inc. →Erving Industries, Inc. notified Vermont consumers of a data breach occurring on July 12, 2024, where an unauthorized third party accessed the network. The incident compromised names. Erving engaged third-party cybersecurity experts, reported the incident to federal law enforcement, and provided 24 months of credit monitoring and identity protection services to affected individuals.
Vermont clock✗ VT AG >45 bday11 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
Linked disclosures
Why this link?Regulatory filings (1) · sorted by filing gap
- bd_d6cfe988740398c0New Hampshire State AGfiled 2024-09-25Verified
Source provenance
- Source URL
- https://ago.vermont.gov/document/2024-09-25-erving-industries-data-breach-notice-consumers
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Sep 25, 2024
- Raw hash
- cfe425aa98185d302823d65b04900fd8cfd2abf17220029d5d5c350622507062
Reporting entity
- Name
- Erving Industries, Inc.norm: erving industries
Victim entity
- Name
- Erving Industries, Inc.norm: erving industries
Incident
- Discovered
- Jul 12, 2024
- Materiality determined
- Sep 16, 2024
- Notification sent
- Sep 16, 2024
- Affected individuals
- Not disclosed
- Data types
- IDENTITY_BASIC
- Attack vector
- Unauthorized Access
- MITRE ATT&CK
- T1190 Exploit Public-Facing Application
- Threat actor
- External
- Regulator citations
- reported this incident to federal law enforcement
- Initial access
- exploit_public_facing
Compliance
- Time to disclose
- 11 weeks(75 days from discovery to filing)
- Compliance flags
- VT AG >45 bday
- 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.