MediumII Cyber Warfare & Critical Infrastructure18 November 2026, Wednesday
Attackers hijack PayU payment interface and drain 25.67 crore rupees
Gurugram cyber police said on 18 November that attackers who breached payments company PayU's cloud servers moved 25.67 crore rupees into unauthorised accounts. Only about 1.5 crore rupees has been frozen so far.
According to police information cited by MediaNama, the attackers accessed three cloud servers and tampered with PayU's payout API. The API is the software interface companies use for automated money transfers. The attackers added new beneficiary accounts and made 265 unauthorised transfers to 156 bank accounts. PayU's security team noticed the unusual activity at around 23:30 on 5 November, by which time the transfers had gone through. The company filed a complaint on 9 November.
Daily Pioneer, citing PTI, reports that police arrested two people in Ludhiana on 15 November. Neither breached the servers; they supplied a chain of bank accounts to receive the money in exchange for a 2% commission. Police found 6.20 lakh rupees in one suspect's account. An audit report showing how the breach happened is awaited. PayU has made no public statement.
The constraint is oversight of payment APIs. On 9 October CERT-In and CSIRT-Fin warned of identity theft and mule-account attacks targeting payment APIs; whether this attack exploited those weaknesses could not be verified. MediaNama reports that a confidential RBI circular dated 3 November made pre-registration of beneficiary accounts mandatory. Existing API integrations must put these safeguards in place by 3 December 2026.
Talay assessment
Bottom line
The PayU case follows the same pattern as the attacks on NBFCs in Delhi: the attacker targets the institution's automated payment interface, not customer accounts. Only about 1.5 crore rupees of the 25.67 crore has been frozen, as a chain of mule accounts disperses the money quickly. The real test is the RBI's 3 December deadline for API safeguards. Similar cases continuing until then is the most likely path.
Likely effects
- Payment firmsNegativeWeeks
The RBI's beneficiary registration and extra approval requirements force payment companies to rebuild their API integrations by 3 December.
- Fund recoveryNegativeWeeks
The 265 transfers were spread across 156 accounts and only 1.5 crore rupees was frozen; the market for mule accounts limits recovery.
- RegulationUncertain1–6 months
A run of API cases could push the RBI to turn its confidential circular into a binding, public directive.
Possibilities, ranked
- 1Cases continue, deadline holds55%
New API cases emerge before 3 December and the RBI enforces the rules without extending the deadline.
Watch: New payment API breach reports before early December and any RBI statement on the deadline
- 2RBI hardens the rules30%
The RBI converts the circular into a public directive backed by penalties.
Watch: The RBI publishing a formal circular on payment API security
- 3Deadline extended15%
Under industry pressure, the RBI postpones the 3 December deadline.
Watch: A payments industry body requesting an extension and the RBI's response
Probabilities are calibrated judgement based on the sources, not measurement, and are revised as new information arrives. Not investment advice.
Market reaction
Indicators affected
- Amount drained▼ 25.67 crore rupees
- Unauthorised transfers▼ 265
- Amount frozen▲ ~1.5 crore rupees