Stitch

Stitch 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.

Stitch Connect Inc. reported a data breach to the Vermont Attorney General. The breach was reported to the AGO on 2026-10-23. The reporting organization type is Other Commercial. 86 Vermont residents were affected. Categories of data breached: Health Records.

Stitch Connect Inc reported a hacking incident on September 18, 2026, where attackers accessed profile information (names, photos, bios, interests, location) and private messages for a small percentage of members. Passwords and credit card information were not accessed. The company blocked the attacker, removed malicious accounts, and closed the exploited entry route.

Stitch Connect Inc based in San Francisco, California, a business – retail or merchant entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-09-18 and reported on 2026-10-16. 4,062 Texas residents were affected. 113,727 individuals affected in total. Types of information involved: Name of individual;Medical Information;Date of Birth. Consumers were notified via Email.

Stitch Connect Inc reported a hacking incident where attackers accessed private messages and profile information (first name, photos, bio, interests, suburb location) of a small percentage of members. No passwords, credit card information, email addresses, or phone numbers were accessed. The attacker was blocked, malicious accounts removed, and the access route closed. The incident is contained.