PennyMac Loan Services, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-21. The breach occurred on 5/30/2023. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Aug 21, 2023 → Aug 28, 2023. View entity profile → Other incidents for this victim →
incident inc_4466fbb7d6c44b3c · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 30, 2023
When the intrusion reportedly occurred, per the linked filings
May 30, 2023
Reported by CALIFORNIA AG filing
PennyMac Loan Services, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2023-08-21. The breach occurred on 5/30/2023. 1 Montana residents were affected.
Affected (this filing): 1
Sovos Compliance, LLC, a vendor for PennyMac Loan Services, LLC, experienced a security incident on May 30, 2023, when unauthorized actors exploited a previously unknown vulnerability in Progress Software's MOVEit Transfer application. The attackers downloaded a file containing personal information of PennyMac customers. Sovos took the application offline, activated incident response, retained experts, and notified law enforcement. Credit monitoring services are being offered 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.