Financial institution · Banking and financial services · Commercial banking network · Global

QNB Group (Qatar National Bank) Data Breach (2015)

Qatari banking group offering retail, corporate, and investment banking services.

Pilot record · BRI 2.0 results pending
Breach Risk Index
LowGuardedElevatedHighSevere
Not yet scored
Circulation not yet audited
What this rating measures

The Index rates how dangerous a breach is right now rather than how large it was. It values each exposed field on its own, ages each one according to what that field is, and models what the assembled set lets an attacker do.

It is read against what is observed circulating, not what was announced. Five bands run from Low through Guarded, Elevated and High to Severe.

Every rating carries a status. Observed means it rests on fields seen circulating. Observed minimum means at least that much was seen, so read it as a floor. Provisional means the field list comes from breach catalogues and is not yet verified. How sure we are of the evidence is shown separately, and it never lowers the rating. How the Index works →

Data sensitivity
Restricted

Includes data that cannot be reissued or taken back. A changed password does not reach it.

Volume
Count not yet verified
Field types
16 listed
Breach date
Jul 2015
Attributed
Unknown (SQL injection; Bozkurtlar-aligned per public reporting)
Catalogued by Have I Been Pwned
How it unfoldedAbout 10 months from breach to listing
  1. 10 months laterBreach
  2. Listed in breach catalogues
What came out

What data was exposed

Government IDCannot be reissued
Date of BirthCannot be reissued
Home addressWhere you sleep
Bank Account NumberFinancial
Transaction History (financial transaction)Financial
PINCredential
PasswordCredential
Security Question / AnswerCredential
Full NameIdentity
Geographic locationLocation
IP AddressDevice
Phone NumberContact
Relationship StatusDemographic
GenderDemographic
Spoken LanguageDemographic
Customer Service Records (customer feedback)Notable exposure
Red cannot be reissued or taken back · Blue is the residence · Black is movement, where you go rather than where you live · Grey is high-signal data that is not standard breach material · Field list from breach catalogues, not yet verified
What it enables

How this data can be used against you

Assessed once the record is scored.

What you should do

Three key actions to take

Assume your home address is findable

Be wary of unexpected visitors, deliveries or messages that mention where you live. Ask people-search sites to remove your address, and check again every few months, because listings come back.

Change your QNB Group (Qatar National Bank) password

Change it anywhere you reused it too, and turn on two-step sign-in.

Ask about a new ID number

Your state DMV may issue a new driver's license number after a breach. Watch for accounts opened in your name.

Check it yourself

Check whether you were affected

Most people in a breach like this do not need an engagement. They need to know whether their address is in it, and when it turns up somewhere new. HackNotice does both, free: an Instant Check now, alerts after.

HackNoticeRuns on HackNotice · ObscureIQ never sees the address you check
Run the Instant Check →
If this matters to you

Talk to us about your exposure

If you are exposed in a way that cannot be rotated away, or you are responsible for someone who is, a call establishes what is actually reachable about you and what is worth doing first. No charge for the conversation.

Request a confidential call →
Full record · 9 sections

The full breach analysis

What happened, what the company reported against what is circulating, the field-by-field record, the actor and the advisory.

  • What happened
  • Recent developments
  • Reported and circulating
  • Data points exposed
  • Downstream risk
  • Principal risk advisory
  • Threat actor
  • Background
  • Data context
No sign-in · nothing is recorded
What happened

How this breach happened

Qatar National Bank, the largest bank in the Middle East and Africa region, suffered a data breach in July 2015 that became public in April 2016 when the stolen data was published on a file-sharing site. The dataset comprised approximately 15,000 documents totaling 1.4 gigabytes and detailed more than 100,000 customer accounts. Analysis suggested the attack began with a SQL injection flaw in the bank's web infrastructure, which gave the attacker access to internal databases that were then progressively exfiltrated.

The exposed records included bank account numbers, customer names, dates of birth, government-issued identification, addresses, phone numbers, email addresses, IP addresses, gender, marital status, language, security questions and answers, transaction histories, account passwords, and PINs. Have I Been Pwned indexed approximately 89,000 unique email addresses among the records. The data also contained folders flagged with labels suggesting connections to Al Jazeera staff and intelligence services, drawing additional regional press attention beyond conventional breach coverage.

For affected individuals, the practical risk profile is exceptionally severe because the leaked dataset combines complete account credentials with transaction histories. The combination of bank account number, PIN, security question answers, and password supports direct account takeover by anyone in possession of the data. Government identifier and demographic fields support identity-verification bypass at other financial institutions. While much of the original credential data is now a decade old and presumably reset, the demographic and transaction-history records remain durable identity-fraud assets. Anyone who held a QNB Group account during the affected period should treat their identity data as exposed and remain alert to any unsolicited contact referencing past Qatar-region banking activity.

Recent developments

What has happened since the breach

QNB Group has continued to operate as one of the leading banks in the Middle East and Africa region in the years since the 2015 incident, and the 2016 public exposure of the data did not appear to materially disrupt its business growth. The bank issued a statement at the time emphasizing that its core banking and payment systems were not compromised. QNB has not been publicly tied to a further large-scale data breach disclosure since then. Reporting at the time noted that the leaked dataset included flagged entries for individuals associated with Al Jazeera staff and a separate folder labeled 'spy, intelligence' that drew significant local and regional media attention.

Reported and circulating

What was reported vs. what is circulating

The company's notice

Reported

Status
Not yet researched
Not yet verified by ObscureIQ

Listed in breach catalogues

Breach date
Jul 2015
Volume
Count not yet verified
Fields listed
16bank account number, customer service records (customer feedback), date of birth, full name, gender, geographic location, government ID, IP address, password, phone number, home address, PIN, relationship status, security question / answer, spoken language, transaction history (financial transaction)

The score is built only on what is listed in circulation.

Data points exposed

Every exposed field, and how long it stays useful

FieldShelf lifeIn noticeListed
Bank Account NumberLasts for yearsNoYes
Customer Service Records (customer feedback)Lasts for yearsNoYes
Date of BirthLasts for yearsNoYes
Full NameLasts for yearsNoYes
GenderFades over a few yearsNoYes
Geographic locationLasts for yearsNoYes
Government IDLasts for yearsNoYes
IP AddressExpires fastNoYes
PasswordExpires fastNoYes
Phone NumberFades over a few yearsNoYes
Home addressLasts for yearsNoYes
PINFades over a few yearsNoYes
Relationship StatusFades over a few yearsNoYes
Security Question / AnswerLasts for yearsNoYes
Spoken LanguageLasts for yearsNoYes
Transaction History (financial transaction)Lasts for yearsNoYes

Shelf life is how long a field stays useful to someone holding it. A password expires fast. A government ID number or a date of birth lasts for years. An address stays useful long after it stops being current.

Downstream risk

How attackers can use this data

High risk of financial fraud, identity theft, and targeted phishing. Exposure of banking data significantly increases the likelihood of account compromise and social engineering attacks.

Principal risk advisory

Risks for executives and other high-profile people

A financial-institution breach: account, wealth or payment data supports direct fraud and highly credible financial-impersonation scams. For a high-profile principal this is targeting-grade, not merely identity-theft-grade: the combination lets an adversary locate, impersonate, or pressure the principal with little additional work.

Threat actor

Who is behind this breach

Attributed to Unknown (SQL injection; Bozkurtlar-aligned per public reporting).

Background

About the company

Qatar National Bank, known as QNB Group, is the largest financial institution in the Middle East and Africa region by assets. Headquartered in Doha and founded in 1964 as Qatar's first domestically owned commercial bank, it is jointly owned by the Qatar Investment Authority and public shareholders. The group offers retail, corporate, and investment banking services and operates an international network spanning roughly thirty countries across the Middle East, Africa, Europe, and Asia. As a flagship financial institution, QNB processes substantial volumes of customer identity, account, transaction, and authentication records, including bank account numbers, transaction histories, and payment-card data.

Data context

Why the company holds this data

Financial institutions store highly sensitive data including identity documents, account details, transaction history, and authentication credentials.

Unknown (SQL injection; Bozkurtlar-aligned per public reporting)Financial ServicesBankingPublic company2015

About this record

No reported total is on record for this breach. No count has been verified for this breach yet. Figures in older breach catalogues are not shown until they are checked against the data. No score is shown until the circulating field list has been audited. Scores come from the Breach Risk Index, which rates what the exposed fields still let an attacker do, not how large the breach was. Breach records change as evidence does. If you hold a notice, a filing or a dataset observation this page does not reflect, report a correction.

ObscureIQ · Circulating breach record How the Index works · Contact MMXXVI