Security researcher Jeremiah Fowler uncovered an openly accessible database containing 13.7 million records harvested from previous data breaches. The archive, hosted on an IP linked to Indian software platform Vibetech, included passwords, banking details and personal identifiers tied to corporations such as AT&T, Amazon, Walmart and PayPal. After Fowler’s disclosure, the database was secured, but the incident highlights the persistent danger of unprotected breach repositories.
Key Takeaways
- 13.7 million compromised records were publicly reachable before being taken down.
- AT&T accounts dominate the leak with nearly eight million entries; Amazon, Walmart and PayPal follow.
- The data originated from multiple historic breaches and was aggregated by Vibetech without authentication.
- Unsecured breach archives remain a leading vector for credential theft and financial fraud.
| Metric | Value | Why it matters |
|---|---|---|
| Records exposed | 13.7 million | Scale of potential credential abuse across multiple industries. |
| Primary source company | AT&T (≈8 million records) | Largest single‑entity impact, affecting telecom customers. |
| Researcher who reported | Jeremiah Fowler | Known for locating non‑encrypted, public databases. |
| Platform linked to leak | Vibetech (Indian software development platform) | Illustrates how third‑party services can unintentionally expose data. |
What the leaked archive contained
The repository held a “collection of highly sensitive data from previous breaches,” according to Fowler’s analysis. Items included full names, phone numbers, email addresses, clear‑text passwords, and bank account details. A limited sample revealed credentials from multiple countries, indicating a global reach. The data were organized by compromised organization, with the following breakdown:
- AT&T – roughly eight million records
- Amazon – 1.2 million records
- Walmart – 420 000 records
- BluBank Digital Bank – 24 000 records
- PayPal – 18 000 records
- FBI Employee Directory – 4 084 records
- Interpol – 929 records
Unlike typical breach dumps that omit passwords or financial details, this archive combined both, dramatically increasing its utility for threat actors seeking to hijack accounts, deploy ransomware or siphon funds directly.
How the archive was discovered
Fowler, who specializes in locating unsecured databases, identified the dataset while scanning for non‑encrypted storage endpoints. The IP address hosting the database was traced to a data‑intelligence service operated by Vibetech. Upon notification, Vibetech and the hosting provider restricted access, replacing the plaintext dump with an Information Security Management System (ISMS) compliance dashboard within 24 hours.
Vibetech’s role and the legality question
Vibetech appears to have aggregated publicly available breach data into a single repository, a practice that sits in a legal gray area. While some organizations collect compromised credentials for threat‑intelligence research, the lack of authentication and the accidental public exposure of raw data raise serious ethical and regulatory concerns. Fowler notes that such collections “can provide valuable insights into attack trends, credential reuse, and emerging threats,” but also stresses the “legally and ethically complex environment” surrounding the handling of personal information obtained from illicit breaches.
Unprotected databases as a systemic risk
Open or misconfigured storage buckets continue to be a primary cause of large‑scale data exposure. Historical examples include:
- Early 2024 – an Elasticsearch index containing personal data on roughly 223 million Brazilians was discovered, potentially covering the entire national population.
- 2021 – a B2B marketing firm, OneMoreLead, left an AWS‑hosted database exposing up to 126 million U.S. citizens’ email addresses, home addresses and phone numbers.
These incidents demonstrate that the problem is not isolated; rather, it reflects a broader pattern of organizations assuming cloud providers will automatically secure data, or simply overlooking proper access controls.
Why it matters
The exposure of 13.7 million records underscores the tangible risk that unsecured breach archives pose to individuals and enterprises alike. Password reuse across services means a single compromised credential can cascade into multiple account takeovers. Banking details further enable direct financial theft. For businesses, the presence of such data in the public domain can amplify phishing campaigns, increase ransomware success rates, and erode customer trust. Regulators may also scrutinize entities that aggregate and expose compromised data, potentially leading to enforcement actions under data‑protection statutes.
Frequently asked questions
Who discovered the vulnerable database?
Security researcher Jeremiah Fowler, known for tracking non‑encrypted, publicly exposed databases, identified the archive.
What types of data were included in the leak?
The dump contained personal identifiers (names, phone numbers, email addresses), clear‑text passwords and banking details such as account numbers.
Which companies were most affected?
AT&T accounted for the largest share with nearly eight million records, followed by Amazon (1.2 million), Walmart (420 000), BluBank Digital Bank (24 000) and PayPal (18 000). Smaller subsets originated from the FBI Employee Directory and Interpol.
How did Vibetech become involved?
The IP address serving the database was linked to a data‑intelligence platform operated by Vibetech, suggesting the company aggregated breach data and inadvertently left it publicly accessible.
What steps should individuals take if they suspect their data is in the leak?
Affected users should change passwords on all accounts, enable multi‑factor authentication where possible, monitor financial statements for unauthorized activity and remain vigilant for phishing attempts.
Bottom Line
The public exposure of 13.7 million compromised records—many with passwords and banking details—demonstrates how aggregating breach data without proper safeguards can amplify cyber‑risk. While Vibetech’s platform quickly restricted access after notification, the episode reinforces the need for rigorous data‑handling policies, especially when dealing with historically leaked information.
Reporting based on: original source.
Comments
Post a Comment