Coriolis Telecom 2025 Dataset Exposure
The Coriolis Telecom dataset exposure is associated with a report that a threat actor offered a dataset claimed to belong to Coriolis Telecom customers on 11 July 2025. ZATAZ published the claim on 12 July 2025.
The affected total is not confirmed, so severity cannot be determined from a record count alone.
Exposed Data Types
8- Email addresses
- Names
- Phone numbers
- Physical addresses
- Dates of birth
- Bank account details
- Company names
- Customer numbers
About This Record
Because Coriolis has not confirmed the incident, LeakData marks this record as unverified.
How was the source bound to the reported event?
The report describes 508,276 records in JSON format with email addresses, IBAN, BIC, contact details, dates of birth, SIRET, and a SEPA-related field. The reviewed Coriolis archive has exactly 508,276 physical lines, the same JSON scale, and the same field set. This conjunction binds the source to the reported 11 July listing with high confidence, but it does not turn the criminal claim into operator confirmation or a verified affected-person count.
What data is searchable in LeakData?
The exact root $.email path was reviewed across the complete single data member. Two independent compiled parsers agreed byte-for-byte on 393,928 valid email occurrences and 361,136 sorted unique canonical email addresses. LeakData imports only those email addresses; names, phone numbers, addresses, dates of birth, bank details, company fields, and customer numbers are not added to the search index.
How many people were affected?
No verified unique affected-person total is known. The 515,927 logical JSON objects result from some physical lines containing multiple adjacent objects. None of the physical-line, object, or unique-email counts is used as a person count, so pwnCount remains unknown.
What does a match mean?
A positive result means the queried email address appears in the processed dataset reported as Coriolis data; it does not by itself prove customer status or the accuracy of any other field. Unexpected bank, payment, or account messages claiming to be from Coriolis should be verified carefully, and multi-factor authentication should be enabled on relevant accounts.
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
