Breach Intelligence

2,848

Total breached databases

PayHere 2022

PayHere 2022

In late March 2022, the Sri Lankan payment gateway PayHere experienced a significant data breach. The platform, which facilitates online payments for merchants and businesses, reportedly had more than 65GB of payment records exposed. The breach affected over 1.5 million unique email addresses. Among the compromised data were names, phone numbers, geographic locations, IP addresses, purchase histories, and partially obfuscated credit card details, including card type, the first six and last four digits, and expiry dates. Additional exposed information is believed to include social media profiles, government-issued identification numbers, birthdates, and business-related information.
  • Data: Company Information Credit Card Information Email Addresses Geographic Locations Government IDs IP Addresses Names Order Information Payment Information Phone Numbers Physical Locations Social Profiles Websites
  • Imported:
  • Records Imported: 17,560,899
  • Number of lines: 148,656,634
  • Size: 65.38 GB
  • Passwords: No

Check if your data appears in this data breach!

Fields count statistics

Numbers may not be precise, a precision threshold of 100 is used to determine if a field is unique.

geo.city top values

domain top values

geo.country top values

Only the top 100 values are displayed in the chart.
Values with less than 100 occurrences are not displayed.

Frequently Asked Questions

A data breach is unauthorized access to data (often involving account takeover, malware, or misconfigured infrastructure). A data leak is exposure of data due to mistakes like public cloud storage, open databases, or accidental publishing. A database dump is a packaged dataset that may come from a breach, leak, scraping, or aggregation.

Change passwords for any affected accounts immediately, prioritizing email, banking, and any account that shares the same password. Enable multi-factor authentication wherever possible. Monitor your accounts for suspicious activity and consider placing a fraud alert or credit freeze if financial data was exposed.

Start with containment and verification: confirm what data was exposed, identify the entry point, rotate credentials (especially SSO, VPN, email), and enforce MFA. Then investigate affected systems, notify stakeholders as required, and harden controls to prevent recurrence. A structured incident response plan helps keep the work measurable and compliant.

Dark web monitoring helps you spot exposure signals early — before stolen data is widely reused for account takeover or targeted attacks. Monitoring complements vulnerability management by revealing when attackers already have leverage. Pair it with continuous attack surface monitoring and strong Asset Discovery to reduce blind spots.

Not always. Some datasets are old, incomplete, or derived from third parties. However, any exposure increases risk because credentials and personal data can be reused indefinitely. Treat it as a priority signal: rotate credentials, enforce MFA, review suspicious logins, and audit the systems that could have produced the data.

SynScan helps you connect the dots between attack surface exposure, vulnerabilities, and breach signals so you can prioritize remediation and reduce the chance of repeat incidents.