Confirmed breach. Intrusion Nov 27, 2021, discovered Nov 28, 2021 — the first regulatory filing landed 71 days later. 3 individuals reported across the linked filings.
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.
Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
3
Data types
—
Jurisdictions
2
MT SC
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Nov 27, 2021
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Nov 28, 2021
Reported by SOUTH CAROLINA AG filing
71 days
🌴South Carolina State AGFirst filinglinked via multistate filing link · 100%
KMG Prestige, Inc. notified South Carolina residents of a ransomware incident discovered on November 28, 2021, affecting systems on November 27, 2021. Impacted data included names, driver's license numbers, SSNs, and health insurance info. The company engaged forensic experts and the FBI, restored systems, and offered 12 months of credit monitoring.
KMG Prestige, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2022-02-07. The breach occurred on 11/28/2021. 3 Montana residents were affected.
Affected (this filing): 3
Leak >30d
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.