Case Library / Deepfake & Synthetic Media / Ahmedabad Aadhaar deepfake fraud: AI blinks beat face checks (2026)
Deepfake & Synthetic Media Documented incident

Ahmedabad Aadhaar deepfake fraud: AI blinks beat face checks (2026)

Police say a gang turned photos into AI blinking clips to beat Aadhaar face checks, hijack linked phone numbers and take loans. Seven arrests so far.

Share:

Social Engineering Examples·7 sources

An Ahmedabad businessman's bank OTPs went quiet in April 2026. The reason: someone had swapped the mobile number tied to his Aadhaar ID, without asking him, and taken a Rs 25,000 loan in his name. Police say an interstate gang was behind it. Their trick was to turn ordinary photos into short AI clips of a face blinking, hold them up to Aadhaar's face check, and pass as the real person. From there, the new phone number caught every OTP. By 8 May 2026, seven arrests. Status: Alleged; arrests, no convictions yet.

Key takeaways

  • Nobody was conned face to face. The thing being fooled was a machine.
  • Police say one still photo and a free AI tool produced a convincing "live" blink.
  • Control the phone number and you control the OTPs. That was the whole prize.
  • Rs 10 to 15 lakh a year is the police's own estimate of the racket's take, not a court figure.

How the scheme worked

Job What police say it involved
Data Aadhaar numbers, phone numbers and photos, pulled from leaks, business lookup sites, credit reports and apps such as WhatsApp, Instagram and Truecaller
Kits Genuine Aadhaar update kits, the sort used at service centres
Fake A victim's photo fed into consumer AI, reportedly Google Gemini and Meta AI, to make a blinking clip
Bypass That clip shown on a screen to the kit's camera, passing the "is this a live person" test
Takeover The Aadhaar-linked mobile number changed to one the gang held
Cash Small instant loans, usually Rs 25,000 to 50,000, applied for with the hijacked OTPs

Lenders named in the reporting, among them IDFC First Bank, Kotak Mahindra Bank, City Union Bank, Jio Payments Bank and several lending apps, were on the receiving end of fraudulent applications. Nothing suggests they were in on it. Related reading: synthetic identity and account takeover.

Tip: OTPs that stop turning up out of nowhere aren't a network glitch to shrug off. Check your Aadhaar-linked number that day.

How it was found

A 36-year-old from Thaltej went to Ahmedabad Cyber Crime Police on 10 April 2026. His Aadhaar number had a new phone attached, his OTPs had dried up, and his DigiLocker and bank access were exposed. Weeks later his credit report showed enquiries he didn't recognise, plus a Rs 25,000 loan through Jio Payments Bank. Four arrests followed on 29 April. Three more, picked up in Uttar Pradesh and Assam, came on 7 and 8 May. One suspect was still on the run, according to reports. Since no one has been convicted, the names stay off this page.

What stops it

  • Liveness checks that can spot a screen, not just a face.
  • A heads-up to the old number whenever the Aadhaar-linked one changes.
  • UIDAI's biometric lock. Switch it on and only unlock when you need it.
  • A glance at your credit report every few months. Strange enquiries show up there first.
  • Fewer clear, front-facing photos online, where that's realistic.

Also see deepfake vs synthetic media.

Common questions

How did the gang beat Aadhaar's face check?

By police account, they made short AI videos of victims blinking from ordinary photos and showed them to the camera.

What was the goal?

Taking over each victim's Aadhaar-linked phone number, so OTPs came to the gang and loans could be taken out in the victim's name.

How many arrests?

Seven by 8 May 2026. One more suspect was reported to be at large.

What can I do to protect my Aadhaar?

Lock your biometrics with UIDAI, treat missing OTPs as a red flag, and look over your credit report for loans you never took.

Sources

Provenance. This case rests entirely on secondary news reporting; no FIR, court filing, or police press release is directly cited here, only journalists' quotes from investigating officers.

Cite this case

Social Engineering Examples. “Ahmedabad Aadhaar deepfake fraud: AI blinks beat face checks (2026)”. Accessed 3 November 2026. https://socialengineeringexamples.com/ahmedabad-aadhaar-deepfake-ekyc-loan-fraud-2026

Attack Chain & Defense
1Data harvesting
What happened

A data-broker role sourced victims' Aadhaar numbers, PAN/GST details, and photographs, reportedly via data leaks, commercial GST/PAN lookup platforms (MastersIndia, Peridot), and CIBIL/CRIF High Mark credit-report pulls, plus photos scraped from social and payment apps (WhatsApp, Instagram, Facebook, PhonePe, Google Pay, Truecaller).

The control that would have stopped it

Restricting and auditing bulk/anomalous queries on commercial GST, PAN, and credit-bureau lookup platforms (MastersIndia, Peridot, CIBIL/CRIF High Mark) for patterns tied to a single requester is the most practical control here; leaked PII and scraped social/payment-app photos are very hard to eliminate at the source.

2Aadhaar-linked number identification
What happened

The gang is reported to have used bot-driven lookup tools on messaging platforms to confirm which mobile number was actually registered against a target's Aadhaar, narrowing which number needed to be hijacked.

The control that would have stopped it

Telecom and messaging-platform operators monitoring for automated bot activity that maps identities to registered mobile numbers, and rate-limiting such lookups, though this is a supporting control rather than a full stop given how distributed such tooling is.

3Kit access
What happened

A separate kit-runner role procured genuine Aadhaar Update Client Lite (UCL) enrolment kits normally issued to Common Service Centre operators, giving the gang legitimate-looking hardware/software access to Aadhaar's update and liveness-check pipeline.

The control that would have stopped it

Tightening access controls, credentialing, and audit trails over who can operate Aadhaar UCL enrolment kits at CSC centres, since kit diversion is the point where a "legitimate" tool enters the fraud chain and is realistically the more controllable choke point than the underlying data leaks.

4Deepfake generation
What happened

A technical operator fed a victim's static photograph into consumer generative-AI tools (Google Gemini, and in the expanded case Meta AI) to produce a short synthetic "eye-blink" video simulating a live face.

The control that would have stopped it

Consumer generative-AI platforms' own misuse-detection and provenance tooling (for example, watermarking or flagging repeated face-animation generation from a single uploaded photo) could catch this pattern, though it is hard to close completely given the tools' legitimate uses; the more reliable control sits downstream at the verification step itself (Stage 5).

5Liveness bypass and mobile-number takeover
What happened

The synthetic video was displayed on a screen to the UCL kit's camera to pass Aadhaar's facial-liveness verification, and the fraudulently re-verified session was used to change the victim's Aadhaar-linked mobile number.

The control that would have stopped it

Replacing simple static-photo-to-blink liveness checks with randomized challenge-response prompts and multi-frame depth, texture, and lighting-consistency analysis would make a screen-replay deepfake far harder to pass, and any Aadhaar mobile-number-change request should itself be treated as a high-risk event pending secondary verification.

6OTP interception and account access
What happened

With the number redirected, OTPs intended for the real Aadhaar holder went to the fraudsters, giving them access to DigiLocker, UIDAI services, and e-KYC flows at banks and lending apps.

The control that would have stopped it

Step-up authentication and fraud alerts on DigiLocker, UIDAI, and bank logins immediately following an Aadhaar mobile-number change, plus notifying the old number/email of the change before it takes effect, would give the real holder a chance to catch the takeover before OTPs are misused.

7Fraudulent loan origination
What happened

The gang used the hijacked identity to open bank accounts and apply for small instant personal loans (typically Rs 25,000-50,000) at multiple banks and fintech lenders in the victim's name.

The control that would have stopped it

Lenders adding secondary out-of-band verification, such as a callback to a previously-known number or a live human video-KYC review, before instant-loan disbursal rather than relying on e-KYC/OTP alone, and both lenders and consumers monitoring credit reports for unexpected enquiries, as happened in the seed case.

8Cash-out and laundering
What happened

Proceeds from the fraudulent loans were routed through multiple accounts, including one held by an accused acting as a money mule, to obscure the trail before the racket was disrupted.

The control that would have stopped it

Standard anti-money-laundering transaction monitoring on receiving accounts for the sudden appearance and rapid pass-through of freshly disbursed loan funds is the realistic backstop once the earlier controls have already failed, since tracing funds after multiple hand-offs is much harder than catching the fraud upstream.

Quick Facts
Victim
Indian digital lending platforms and banks relying on Aadhaar e-KYC/biometric liveness verification for instant loans and account opening
(named: IDFC First Bank, Kotak Mahindra Bank, City Union Bank, Jio Payments Bank, RKBANSAL, True Credits, EarlySalary), plus the individual Aadhaar holders whose identities and mobile numbers were hijacked to obtain the loans
Location
Ahmedabad, Gujarat, India
(accused also drawn from Vadodara, Bharuch, Anand and Jambusar in Gujarat; Kushinagar, Uttar Pradesh; and Morigaon, Assam)
Date
Case registered 10 April 2026
(Ahmedabad Cyber Crime Police Station); first 4 arrests announced 29 April 2026; 3 further arrests announced 7-8 May 2026 (total 7 arrested as of reporting, with one suspect, Oli Ullah, reported still absconding)
Impact
Reporting identified a fraudulent instant loan of Rs 25,000 obtained in a Thaltej businessman's name.
BasismeasuredOne confirmed Rs 25,000 loan; the wider racket total is a police estimate, stated as such
Investigators separately estimated that the racket generated roughly Rs 10 lakh to Rs 15 lakh per year through fraudulent loan transactions; this was a police estimate, not a court-established or audited total.
Status
Documented incident
Case Type
Real-World Incident
Sector
Financial Services & Insurance, Government & Public Sector
Threat Actor
Organized Crime
Explore more

Related Cases

Browse by what this case has in common with others in the library.