Confirmed breach. Intrusion Jun 28, 2022, discovered Jul 4, 2022 — the first regulatory filing landed 21 days later. 5 individuals reported across the linked filings.
incident inc_2a7886e250574011 · merge_method human · confidence 100%
Litigation Timing
Notification delay
21days
Discovered → first regulatory filing
Leak precedence
-44days
Gap between first leak claim and first regulatory filing
Filing span
Regulatory clocksMaine✓ ME AG ≤30d · 21dFull clock table in Litigation Timeline
Leak SiteState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
44days
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Affected (total reported)
5
Data types
2
PII · Government ID
Jurisdictions
2
ME
Linked filings
2
Leak Site · State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 28, 2022
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Jul 4, 2022
Reported by MAINE AG filing
🦞Maine State AGFirst filinglinked via shared-victim match · 100%
SHI International Corp. reported an external system breach that occurred on June 28, 2022, and was discovered on July 4, 2022. The breach affected 5 Maine residents, compromising their names and Social Security numbers. In response, the company offered 24 months of Equifax Complete Premier credit monitoring services to those affected.
Affected (this filing): 5
ME AG ≤30d · 21d
44 days
🌐GLOBALClaimed by Black BastaMost recentlinked via shared-victim match · 100%
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.