← ARCHIVE / CASE-20160229-MATE1
CASE FILE CASE-20160229-MATE1

Mate1.com

mate1.com
CRITICAL SENSITIVE
27,393,015 ACCOUNTS
FEB 2016 BREACH DATE
25 DATA TYPES
1mo DARK PERIOD

EVIDENCE FILE

CASE CONTEXT

This record summarizes the public breach profile for Mate1.com: when it happened, when it surfaced publicly, the estimated exposure, and whether Have I Been Pwned currently marks it as verified. It is a plain-English view for quick risk review and source attribution — it keeps the source data visible, separates the public incident record from recovery advice, and collects nothing about you.

RISK REVIEW

The right response depends on what was exposed. The reported data classes here are Astrological signs, Dates of birth, Drinking habits, Drug habits, Education levels, Email addresses, Ethnicities, Fitness levels, Genders, Geographic locations, Income levels, Job titles, Names, Parenting plans, Passwords, Personal descriptions, Physical attributes, Political views, Relationship statuses, Religions, Sexual fetishes, Travel habits, Usernames, Website activity, Work habits: email addresses and usernames can fuel phishing or account enumeration, profile data helps with impersonation, and financial or government identifiers warrant a closer fraud review. Have I Been Pwned currently marks this breach as verified, which means the service has reviewed the incident record against its source standards.

Because this breach includes password data, reused passwords should be replaced anywhere they appear. A unique password manager entry and multi-factor authentication are the safest follow-up steps. HIBP marks this breach as sensitive. TRACED keeps the public facts readable while avoiding collection of visitor identifiers, passwords, or account lookups tied to a person. For personal cleanup, start with password reuse, two-factor settings, and recovery-email security on the affected service. For research, treat this file as a source pointer and confirm exact impact against the original HIBP entry — the counts here describe the public record, not any one account.

DISCOVERY GAP

DISCOVERY GAPTime between breach occurrence and public disclosure
BREACH OCCURREDFEB 2016
1 month dark
DATA SURFACEDAPR 2016

1 month passed before this incident was disclosed.

REDACTED EVIDENCE

PASSWORD DATA CLASSIFIED
████████████ ████████ ████████████████
████████████████████ ████████████ ████████

If this breach included passwords, treat them as compromised. If they were reused anywhere else, change them there too.

RELATED CASES - 2016