Confirmed breach. Intrusion Jun 13, 2023–Jun 26, 2023, discovered Jul 7, 2023 — the first regulatory filing landed 38 days later. 3 individuals reported across the linked filings.
incident inc_4660cda9c963483e · merge_method human · confidence 100%
Litigation Timing
Notification delay
38days
Discovered → first regulatory filing
Leak precedence
32days
Gap between first leak claim and first regulatory filing
Filing span
Regulatory clocksMaine⏱ ME AG >30d · 38dFull clock table in Litigation Timeline
Leak SiteState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
32days
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)
3
Data types
2
Identity (basic) · 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 13, 2023 → Jun 26, 2023
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Jul 7, 2023
Reported by MAINE AG filing
🌐GLOBALClaimed by AkiraFirst sightinglinked via shared-victim match · 100%
Gerber Childrenswear LLC is a leading marketer of infant and toddler apparel and related products in the marketplace. Almost 0.5TBof data will be uploaded to our blog soon. So detailed business information is there: patents, trademarks, contracts with other business giants. Much to look through.
32 days
🦞Maine State AGMost recentLeaked → filing gap · 32dlinked via shared-victim match · 100%
Gerber Childrenswear LLC reported an external system breach that occurred between June 13, 2023, and June 26, 2023. The breach was discovered on July 7, 2023. The compromised information includes names and Social Security numbers. The company notified affected individuals and offered 12 months of identity protection services through Experian.
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.