Home All Breaches AIType_BF.7z.002

AIType_BF.7z.002

Database World ROC

This page documents a data breach listing tracked by Breach House. It summarizes the publicly advertised leak attributed to Database World ROC, including the affected entity, origin and the date the listing was first indexed.

Country
Discovered
2026-07-01
Breach ID
b96f9d6749a5

Breach Overview

ai.type - database Domain: aitype.com Record count: 20.580.060 Date of breach: 2017-12-05 Compromised data: Address book contacts Apps installed on devices Cellular network names Dates of birth Device information Email addresses Genders Geographic locations IMEI numbers IMSI numbers IP addresses Names Phone numbers Profile photos Social media profiles Description: In December 2017, the virtual keyboard application ai.type was found to have left a huge amount of data publicly facing in an unsecured MongoDB instance. Discovered by researchers at The Kromtech Security Center, the 577GB data set included extensive personal information including over 20 million unique email addresses, social media profiles and address book contacts. Please note that the file shared here is only 30GB. If you have the full thing, please contact. Compressed size: 6.39 GB Uncompressed size: 26.89 GB

Dark Web Exposure

Findings for ai.type — indexed by HaveIBeenRansom.
39
found in Infostealer logs
0
found in Traditional breaches
0
found in Ransomware leaks
Emails exposed
••••
Internal
•••
External
•••
Distinct leaks
••
••••••••••••••••••••••••
•••••••••• · ••••••
••• emails
••••••••••••••••••••••••
•••••••••• · ••••••
••• emails
••••••••••••••••••••••••
•••••••••• · ••••••
••• emails
••••••••••••••••••••••••
•••••••••• · ••••••
••• emails
Full exposure is locked
See every breached email, the internal-vs-external split and each leak source behind this breach.
Want the complete picture — passwords, machines, full leak files? It's all searchable on HaveIBeenRansom.
Search this breach →
Original Post View Group: Database World ROC
Legal Disclaimer: This breach record is compiled from publicly advertised leak listings. Breach.house only records what the operators themselves publish in the open. We take screenshots of their public pages and keep the proof material they post there, so that a listing can be verified and its status tracked over time. We do not purchase data, we do not solicit or encourage its publication, we do not access any private system, and we do not alter anything we record. Nothing is offered for download here, and detailed content is not published on this page or anywhere else on the public site: access to it is restricted to vetted customers under contract, for incident response, due diligence and cyber-resilience work. Breach.house is not affiliated with, and does not act on behalf of, the operators who publish this material. If you represent an organisation or individual named here and want a record reviewed or removed, contact us and we will act on it.