All Breaches
February 26, 2023 Verified Education / Online Community

TheGradCafe Data Breach

The GradCafe data breach is an incident that occurred in February 2023 on The GradCafe platform, which provides community information about graduate applications and admission processes. The record is associated with 310,975 users.

311 Thousand
Reported Records
9
Data Types
High
Severity
Oct 9, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

9
  • Email addresses
  • Genders
  • Geographic locations
  • IP addresses
  • Names
  • Passwords
  • Phone numbers
  • Physical addresses
  • Usernames

About This Breach

Data classes include email addresses, gender information, geographic locations, IP addresses, names, hashed passwords, phone numbers, physical addresses, and usernames. Due to the educational context, the risk of identification and targeting related to the application process is high.

Leaked Data Types and Risks

When the username, email, name, and location information are combined, the online community identity can be matched with the real person profile. The hashed password field poses a risk for other accounts as well if there are password repetitions. Fields such as IP address and physical address make the user's online behavior and location context more visible.

When fields like name, email, phone, or address come together, attackers can approach the user as if there is a legitimate service relationship. This information alone is not proof of account takeover; however, it provides a strong starting point for fake support messages, delivery notifications, password reset attempts, and personalized fraud flows. Since it is related to the registration, training, and application process, fake university communication, admission counseling, application fees, scholarship notifications, or account verification messages may be more convincing. Although it is not expected that every line contains phone numbers and physical addresses, these fields may appear in some records.

Verified Scope and Boundaries

The incident date is February 26, 2023, and the number of affected accounts is recorded as 310,975. Security logs indicate that TheGradCafe personal user data was exposed, passwords were found hashed with bcrypt, and some records may also contain additional fields such as phone number, physical address, and date of birth. The existing data classes are consistent with the main risk areas.

It should not be said that passwords are in plain text when explaining the scope. A hashed password still poses a risk if the password is reused. Additionally, this record does not mean that all application results or private messages have been leaked; it should be evaluated through the user account, profile, and communication areas.

User Groups at Risk

Users at risk are those who have created an account on TheGradCafe during the graduate application process, shared their application experience, or appeared with their username in forum-like areas. Those who use the same username on other academic platforms can be matched more easily.

Users during the application period may be more open to sensitive themed messages such as scholarships, admission, visas, consulting, or application fees. If geographic location and IP information are combined with the context of the local school or country, targeted messages may appear more realistic.

Urgent Measures to Be Taken

Users in the matched field should change the passwords on their TheGradCafe account and on all accounts where the same password is used. Email accounts, university application portals, and educational platforms where payments are made should be checked first. Two-factor authentication should be enabled wherever possible.

Instead of opening incoming links directly, the user should log in through the known web address or application of the relevant service. The fact that the caller knows the name, email, address, or past transaction information does not prove they are trustworthy. One-time verification codes, payment card information, or account passwords should not be shared in any support conversation.

Long-Term Security Strategies

In the long term, a password manager, unique passwords, two-factor authentication on applicable accounts, and the habit of removing unnecessary personal information from accounts reduce risk. Reusing the same email address across different platforms makes it easier to combine different breaches; therefore, using separate email or alias addresses for critical accounts can be considered.

Since usernames used in academic communities can be easily matched with real identities, users should reduce unnecessary personal information sharing on forum profiles. Old application accounts should be closed, security questions should be stripped of predictable personal information, and application portals should be protected with separate passwords.

Record Control and User Action

LeakData check shows whether the queried email address is found in this record or not. A positive result does not necessarily mean that all data fields definitively belong to that user; however, it should be considered a sufficient warning for precautionary measures. A negative result only indicates that there is no match in this dataset and does not rule out the possibility of appearing in other breaches.

A positive result requires caution, especially for messages related to education applications and account security. A negative result means there is no match within this record; the possibility that the same email address appears on other education platforms should also be checked separately.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information