← ARCHIVE / CASE-20160213-VTIGHTGE
CASE FILE CASE-20160213-VTIGHTGE

V-Tight Gel

vtightgel.com
CRITICAL SENSITIVE
2,013,164 ACCOUNTS
FEB 2016 BREACH DATE
5 DATA TYPES
21mo DARK PERIOD

EVIDENCE FILE

CASE CONTEXT

This record summarizes the public breach profile for V-Tight Gel: 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 Email addresses, IP addresses, Names, Phone numbers, Physical addresses: 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 does not currently mark this breach as verified, so the file should be treated as a public archive record rather than an account-specific confirmation.

This public record does not list passwords among the exposed data classes. It can still support phishing, account recovery abuse, or identity profiling when combined with other breach records. 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 year, 9 months dark
DATA SURFACEDNOV 2017

Over 1 year passed before this breach surfaced publicly.

RELATED CASES - 2016