UBL data leak reports: six accounts, Rs 10.45 million, no bank confirmation
If you are a customer of UBL, here’s what is being claimed, and what it would mean for you.
UBL has not publicly confirmed this case. Reporting on a Lahore High Court bail order describes allegations that six customers lost a combined Rs 10,458,500 after duplicate SIMs were issued in November 2025, with internal bank reports cited in court about compromised mobile numbers. A wider leak of all UBL customers has not been established, and the case is still at investigation stage.
— from the group that posted this listing’s own leak-site posting. This is the group’s claim, quoted verbatim; it is not GalaxyWarden’s reporting and has not been independently verified.
Editor’s note: The claims described below originate from a ransomware group’s leak-site posting and have not been independently verified by GalaxyWarden. A listing of this kind is an assertion made by the group during an extortion attempt. It is not evidence that a breach occurred, and we report it as a claim rather than as a finding.
UBL customer?
See what’s already exposed about you — free, 15sWe check your email against known public breach records and the sites that publish your address, then show you what to do about each one. We don’t hold this company’s data. No account, no card.
Here for work? Check a company domain’s exposure.
United Bank Limited has not confirmed this incident in any public statement, support notice, or filing that has been located. According to a Lahore High Court bail order, as reported in August 2026 by Associated Press of Pakistan, The Express Tribune, Daily Pakistan, and TechJuice, prosecutors allege that six UBL customers had a combined Rs 10,458,500 taken from their accounts after duplicate SIMs were issued in November 2025. Those outlets are quoting the court’s recitation of a complaint to Pakistan’s telecom regulator (PTA), a case with federal cybercrime investigators (NCCIA), and UBL’s internal fraud-unit reports — not an announcement from the bank.
According to that same court record as those outlets describe it, original SIMs were blocked and replacements were issued after fingerprint checks at a Jazz franchise in Yazman; banking apps were then set up on new phones. Internal UBL reports dated 30 December 2025 and 29 May 2026, cited inside the order but not released by the company, reportedly described compromised confidential customer information, including the mobile numbers registered on the accounts, and suspicious login records involving a bank employee. A joint raid on 18 November 2025 reportedly recovered SIM-issuing equipment and about 150 suspicious SIMs. The court reportedly refused bail for the employee and granted bail to a franchise-linked accused. Coverage describes the case as still at investigation and trial; these remain allegations, not convictions. Daily Pakistan’s headline of “over Rs 10 crore” does not match the figure in the order: Rs 10,458,500 is about Rs 1.045 crore, not Rs 10 crore.
This is not a confirmed dump of every UBL customer
Most coverage led with a legal label — the court treating customer data as “property” — or with a leak-style headline and a money total. That framing is easy to read as either “the whole bank was emptied onto the internet” or “only six people, so this has nothing to do with me.” According to the reporting, neither is what the court file actually lays out.
Advertisement
Know the day any company files a breach.
Every SEC 8-K Item 1.05 and state breach notification — dated, sourced, and delivered by email + a JSON API the day it posts. Track any company, not just the ones in the news.
GalaxyWarden Signals and RecentBreaches share common ownership.
What those articles are describing is narrower, and in one way more ordinary: six accounts, a copied SIM, and alleged insider access to the phone numbers sitting on those accounts. Banks send login codes to the number on file. If someone can get a working copy of that SIM, the bank’s own codes go to them, and they can add a new phone to the app and move money. That does not require your password to appear in a public dump. It also does not mean every UBL customer’s file was allegedly stolen.
The honest gap is the part no outlet can close. The internal reports cited in court reportedly spoke of leaked confidential customer information and, in the later report, a broader set of accounts. How broad that set was has not been established in the public reporting. Whether fingerprint data was taken from the bank, as opposed to being used at the phone shop’s own scanner, has also not been established. No public contradiction of the investigation facts was reported from UBL, PTA, or NCCIA; defence arguments were made in court and, according to the coverage, partly succeeded for one accused.
For a worried customer, the point the headlines skip is this: not getting a letter from UBL does not tell you that you were unaffected. Reporters did not find a customer notice at all. Silence is not a clearance. And no article can see whether you were among the six.
What to actually expect
- The articles from August 2026 are reporting a bail order about events in November 2025, not a newly announced bank-wide breach. Recycled posts about this case are more likely than a fresh official list of names.
- Do not expect UBL to email you that you were, or were not, one of the six. No such notice has been reported, and there is no public victim list you can check yourself against.
- Calls, texts, or social-media messages that mention this case and then ask for an OTP, a CNIC copy, a password, or remote access to your phone are not part of the investigation. That is a common follow-on scam when bank stories circulate.
- According to the coverage, the case is still at investigation and bail. No conviction has been reported, and recovery of the Rs 10,458,500 has not been reported.
What you can and cannot fix
If confidential details on those accounts were accessed as alleged, that access cannot be undone. A national ID number used to issue a SIM is not something that can be recalled. The court order and the news reports, including a public copy of the order, are already out. Nobody can honestly promise to remove this data. The money already moved from the six accounts cannot be wished back; whether any of it was recovered has not been reported.
- If you have a UBL account, look at it yourself: the mobile number on the file, any device you do not recognise, and transfers you did not make. That is a check of your own banking. It is not a way to see whether you were one of the six, and no outside scan can answer that.
- If your number suddenly died or stopped receiving SMS around early November 2025, take that to your mobile operator and the bank as a possible SIM replacement. Even then, it does not prove you were in this case.
- Do not reply to anyone who cites this incident and then asks for codes, ID copies, or control of your phone. The useful move is to treat those contacts as hostile, not to try to unpublish a court record that is already public.
What the free scan actually returns
Found on people-search siteswe remove these
These listings are live, public, and legal to remove — and removing them is what we do.
Found in breach recordsverifiedreported — unverified
Each record is labeled: confirmed breach data, or an attacker’s claim no one has verified.
Leaked data cannot be deleted from the internet — anyone claiming otherwise is lying. Broker listings can be removed. We do the second, and show you exactly what to fix from the first.
What to do now
Steps that match what this notice says was exposed
Every step below is free and you do it yourself, and none of it depends on UBL.
- Tell your bank before you do anything else. Account and routing details are the fastest-moving of the fields in this notice. Call the number on the back of your card rather than any number in an email, and ask them to watch the account and reissue the card.
One more, whatever was exposed: a breach notice is a favourite disguise for a phishing email. If a message about this arrives, do not use its links — go to the company’s site yourself, or call the number on your statement.
For security and vendor-risk teams: get an alert the day a vendor you watch files a breach with a US regulator or the SEC — the filing itself, dated and sourced, plus an API. GalaxyWarden Signals →
A staff address in a leak usually means a third party was breached, not you — check your own domain’s exposure. Exposure Monitoring →
Report details & sourcing
Related breaches
Facebook — 509 Million Phone Numbers Tied to Real Names (2019, published 2021)
Roughly 20% of Facebook made freely downloadable in April 2021, scraped through a contact-import wea…
Crunchbase Massive Personal Records Leak — January 2026
ShinyHunters exfiltrated approximately 2 million records from the business-intelligence platform Cru…
PayPal SSN Exposure Lasting Six Months — February 2026
A code change at PayPal allowed unauthorized access to Social Security Numbers and account details f…