Crack Community 2013 Data Breach

The reviewed archive explicitly names mybb_users.email, mybb_maillogs.fromemail, mybb_maillogs.toemail, mybb_mysubscriptions_log.receiver_email, and mybb_mysubscriptions_log.payer_email as email fields. Two independent parsers produced 17,171 safe unique email addresses from those fields. The historical user scope was already present; 88 addresses missing from the mail and subscription logs were imported additively. Password, IP, username, payment, and other fields were not added to the search index.

The final mybb_posts INSERT in the main SQL member is truncated. The tables and statements containing the selected email fields are complete, and the truncated final table has no selected email-named field. The completeness claim therefore applies only to the proven email fields, not to the entire database. The catalog total of 19,210 accounts was not fitted to the imported email count.

A positive result means the queried email address appears in an explicitly named email field of the dataset bound to this event. It does not mean the account is compromised today. Reused or similar passwords should be changed on other services, active sessions and recovery channels should be reviewed, and multi-factor authentication should be enabled wherever possible.