Stitch
bd_1e9c3aca2a590253 · schema v1 · pii pii-v2
Full breach record for Stitch →2 incidents on fileStitch Connect Inc discovered on September 18, 2026, that an attacker exploited a vulnerability in its conversations system to create an account and read the most recent private messages of members. The incident affected 122 New Hampshire residents. Data exposed included profile details (first name, photos, bio, interests, suburb, preferences), some dates of birth, and the content of the last message in some conversations, which may have contained contact details, health-related comments, or financial topics. No SSNs, driver's licenses, passport numbers, financial account numbers, or passwords were involved. The company blocked the attacker, closed the vulnerability, implemented two-factor authentication, and removed dates of birth from profile data. Notices were sent to affected residents between September 21 and 23, 2026.
J jump to incidentP pin to compareR raw source
Incident timeline
Sep 18, 2026
Discovered
Oct 23, 2026
Filed
vs. sector median
6 wks faster
Linked disclosures
Why this link?Regulatory filings (3) · sorted by filing gap
- Vermont State AGbd_f65e13573d5ce2612026-10-23Verified
- California State AGbd_3ba9cbacbd69365d2026-10-18 · +5dVerified
- Texas State AGbd_d87a2eabe170706e2026-10-16 · +7dCandidate
Filing propagation · 4 filings · 4 states
View merged incident ↗Pattern: first filing Oct 16 (TX), last Oct 23 (NH) — a 7-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.