FinsamudraNewsroom, home

News · Daily brief

Anatomy of an Insider Siphon: How ₹35 Crore Vanished Silently from PNB Greater Noida

Executive Summary A major operational and internal control failure has emerged at Punjab National Bank’s (PNB) Aichhar branch near Sector Pi-1 in Greater Noida, Uttar Pradesh. Dozens of depositors—primarily farmers who had deposited government compensation payouts for land acquisition—discovered that nearly ₹35 crore had been siphoned off from their savings accounts and fixed deposits without their consent.

FINSAMUDRA DESK · 29 Oct 2026, 6:20 pm IST · 3 MIN

Hero Image
Image: -Finsamudra

Following protests outside the locked branch, the Sector Beta-2 police station registered an First Information Report (FIR). PNB’s zonal leadership suspended multiple staff members, including the Branch Manager, and initiated an emergency forensic audit.

Beyond the headline losses, the incident exposes severe systemic vulnerabilities in branch-level Core Banking Solution (CBS) operations, silent phone-number alterations, and the circumvention of dual-authorization safeguards.


Key Incident Metrics

┌─────────────────────────────────────────────────────────────────────────────┐

│ PNB GREATER NOIDA FRAUD SUMMARY │

├───────────────────────────────┬─────────────────────────────────────────────┤

│ Branch Location │ Aichhar Market, Sector Pi-1, Greater Noida │

├───────────────────────────────┼─────────────────────────────────────────────┤

│ Estimated Fraud Quantum │ ~₹35 Crore across dozens of retail accounts │

├───────────────────────────────┼─────────────────────────────────────────────┤

│ Source of Depositor Funds │ Land acquisition compensation (Authority) │

├───────────────────────────────┼─────────────────────────────────────────────┤

│ Primary Mechanism │ Unauthorized premature FD break & siphoning │

├───────────────────────────────┼─────────────────────────────────────────────┤

│ Alert Failure │ Suppression of CBS SMS debit notifications │

├───────────────────────────────┼─────────────────────────────────────────────┤

│ Regulatory / Police Action │ FIR at Beta-2 PS; Branch Manager suspended │

└───────────────────────────────┴─────────────────────────────────────────────┘


1. The Modus Operandi: Silent Siphoning & Alert Suppression

Initial police disclosures and victim testimonies reveal a classic pattern of insider-assisted operational embezzlement:

  1. Targeting Passive, High-Balance Accounts: Victims were largely rural landholders who received sizable one-time government compensation windfalls (ranging from ₹10 lakh to over ₹1 crore). These accounts typically remain passive, with depositors rarely using mobile banking or daily net-banking apps.
  2. Premature FD Liquidation: Fixed deposits were closed prematurely within the core banking system without signed customer mandate forms, physical passbook verification, or deposit receipt surrenders.
  3. SMS Alert Suppression: Victims reported that they received zero SMS alerts when funds were debited. In banking fraud forensics, this typically points to one of two vulnerabilities:
    • Unauthorized manipulation of the customer’s registered mobile number in the CBS Master Data.
    • Internal routing of transactions through suspense/intermediate accounts where alert triggers are bypassed.

2. The Core Banking Breakdown: Where Did Maker-Checker Fail?

Under Reserve Bank of India (RBI) internal control guidelines, no commercial bank employee can unilaterally liquidate large fixed deposits or transfer funds without secondary authorization:

Maker (Initiator)→Dual-Control VerificationChecker (Approver)→CBS Ledger Execution\text{Maker (Initiator)} \xrightarrow{\text{Dual-Control Verification}} \text{Checker (Approver)} \xrightarrow{\text{CBS Ledger Execution}}Maker (Initiator)Dual-Control Verification​Checker (Approver)CBS Ledger Execution​

The disappearance of ₹35 crore across multiple accounts demonstrates that:

  • Credential Sharing / Password Compromise: In smaller branch setups, operational discipline frequently breaks down, with supervisory tokens or passwords shared to clear operational backlogs.
  • Lack of Exception Flagging: Large premature FD liquidations followed by immediate RTGS/NEFT outflows to unrelated third-party accounts should have triggered automated Anti-Money Laundering (AML) and Early Warning System (EWS) red flags at the Central Fraud Registry or zonal monitoring desk.

3. Depositor Protection & Legal Liability: The RBI Framework

Under the RBI Circular on Customer Protection (Limiting Liability of Customers in Unauthorised Electronic Banking Transactions):

ScenarioCustomer LiabilityBank Obligation

Fraud due to bank negligence/deficiency

Zero Liability

Bank must reverse the debit within 10 working days of notification.

Third-party breach where customer reports within 3 days

Zero Liability

Bank is obligated to credit shadow balance pending investigation.

Customer delay in reporting (>7 days)

Subject to Bank Policy

Resolution governed by Board-approved compensation policy.

Because the PNB depositors did not share OTPs, click phishing links, or authorize debits, the entire burden of proof rests on the bank. PNB will be required to demonstrate system integrity; failure to do so obligates the bank to fully restore the lost principal along with accrued interest.


More on PNB

Every story on PNB →

Sources


Free daily briefing

The day's money story, before the market opens

The same daily intelligence 30,000+ CXOs, DSAs and finance professionals follow on LinkedIn — with the Finsamudra take on what it means for lending.

The Morning Brief · Free

Get India's lending news before your first call

The daily intelligence 30,000+ finance professionals follow on LinkedIn, in one short email from the Finsamudra Desk.