Teracod Data Breach: What Was Exposed

What happened?

In May 2015, almost 100k user records were extracted from the Hungarian torrent site known as Teracod. The data was later discovered being torrented itself and included email addresses, passwords, private messages between members and the peering history of IP addresses using the service.

When did it happen?

The breach date in the public record is May 28, 2016. The record was added to the catalogue on August 22, 2016 and last updated there on August 22, 2016.

What information was reported as exposed?

Avatars
Email addresses
IP addresses
Passwords
Payment histories
Private messages
Usernames
Website activity

These are incident-level categories. The record does not prove that every category was exposed for every affected person.

Who may be affected?

This record may be relevant to people who had an account or other relationship with Teracod or used teracod.org around May 28, 2016. A catalogue entry does not establish that every customer was affected or that every listed data category applied to each person. Compare the record with an official notice addressed to you.

What should you do?

Verify whether the notice applies to you

Compare the organization, dates, and information categories with any notice you received. Use contact details you independently confirm.

Secure affected accounts

Change exposed or reused passwords, begin with your email account, and turn on multi-factor authentication where available.

Review financial accounts

Check statements for unfamiliar activity and contact the card issuer or financial institution through an independently verified channel.

Expect targeted phishing

Treat unexpected breach follow-ups with caution. Do not use links or phone numbers in a suspicious message; contact the organization directly.

Choose actions that match the information involved. If you find signs that someone is using your identity, the Federal Trade Commission provides a personal recovery plan at IdentityTheft.gov.

Sources and review information

Page reviewed September 14, 2026 by the Data Breach Help Editorial Team. Catalogue details reflect the provider record and may change.

Editorial & sourcing policy Corrections policy