HackingDelayed DiscoveryIDENTITY_BASICIDENTITY_GOVERNMENTMediumContained
Peter Pauper Press
bd_41ac449d84973f70 · schema v1 · pii pii-v1
Full breach record for Peter Pauper Press →Peter Pauper Press notified consumers of a data breach occurring on or around January 25, 2025, involving unauthorized access to its network. The incident compromised names and Social Security numbers. The company offered complimentary identity monitoring services and is reviewing security measures. The notice was filed with the Vermont Attorney General on August 18, 2025.
Vermont clock✗ VT AG >45 bday29 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_bb18036865933434New Hampshire State AGfiled 2025-08-19(1d gap)Verified
Source provenance
- Source URL
- https://ago.vermont.gov/document/2025-08-18-peter-pauper-press-data-breach-notice-consumers
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Aug 18, 2025
- Raw hash
- 8e23cfe25c16921f366910622d3e68afa581cd8dea4c6bb48b409e81c8dd5daa
Reporting entity
- Name
- Peter Pauper Pressnorm: peter pauper press
Victim entity
- Name
- Peter Pauper Pressnorm: peter pauper press
Incident
- Discovered
- Jan 25, 2025
- Materiality determined
- Aug 18, 2025
- Notification sent
- Aug 18, 2025
- Affected individuals
- Not disclosed
- Data types
- IDENTITY_BASICIDENTITY_GOVERNMENT
- Attack vector
- Unauthorized Access
- MITRE ATT&CK
- T1078 Valid Accounts
- Threat actor
- External
- Regulator citations
- Filed notice with Vermont Attorney General
- Initial access
- valid_credentials
Compliance
- Time to disclose
- 29 weeks(205 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.