Confirmed breach. Intrusion Aug 20, 2022, discovered Sep 1, 2022 — the first regulatory filing landed 32 days later. 22,865 individuals reported across the linked filings.
incident inc_a48644353c9b4117 · merge_method human · confidence 100%
Litigation Timing
Notification delay
32days
Discovered → first regulatory filing
Discovery variance
0days
Range of discovered_at dates across filings
Leak precedence
Regulatory clocksMaine⏱ ME AG >30d · 32dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline
Leak SiteState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedavoslocker
-84days
Gap between first leak claim and first regulatory filing
Filing span
84days
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
low sensitivity
Affected (total reported)
22,865
Data types
1
Identity (basic)
Jurisdictions
3
ME OR
Linked filings
3
Leak Site · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 20, 2022
When the intrusion reportedly occurred, per the linked filings
Mount Vernon Mills, Inc. experienced an external system breach on August 20, 2022, which was discovered on September 1, 2022. The breach compromised the names and Social Security numbers of 6 Maine residents. Affected individuals were notified on September 29, 2022.
Affected (this filing): 6
ME AG >30d · 32d
🦫Oregon State AGlinked via operator-confirmed · 100%
Mount Vernon Mills, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2022-10-06. The breach occurred during 8/20/2022. The breach was discovered on 9/1/2022. 22,859 individuals were affected. Notice was sent on 10/14/2022.
Affected (this filing): 22,859
OR AG ≤45d
81 days
🌐GLOBALClaimed by AvoslockerMost recentlinked via operator-confirmed · 100%
stablished in 1947 and headquartered in Mauldin, South Carolina, Mount Vernon Mills is a textiles manufacturer, producing chemicals, textiles, and...
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.