One leaked key. ₹30 Cr gone in minutes.
Exposed API keys, partner access and machine-speed fraud: what the 2026 attack wave means for every lender and how to stop it.
Published 10 November 2026, MIT-TA-2026-11, 16 pages, Mitigata Threat Research
In plain words
A payments company left the secret code that lets its systems move money in a place where outsiders could find it. Someone found it and moved more than thirty crore rupees out in minutes. Every lender holds codes of this kind. The report explains how to find them, who should own each one, and how to stop a stolen code from moving money.
For business leaders
An Indian B2B payments platform lost more than ₹30 crore in minutes after its live payment-gateway secret leaked. There was no malware and no phishing, and every request looked legitimate. Any key that can move money or read customer data is a privileged identity, and CERT-In warned of the same pattern in October 2026. The report sets out ten cyber risks that NBFC boards must own, each with a recent Indian incident, and a 24-point checklist. Ask for an inventory of every live key with a named owner. Ask for rotation of any key that ever sat in an app, a repository or a chat. Ask for payout limits and alerts on new beneficiaries.
For security analysts
Initial access was a live payment-gateway API secret exposed in code, an app build, a log or a config (ATT&CK T1552, T1078). The attacker then called money-movement APIs directly from whitelisted infrastructure. No KYC, beneficiary or velocity check stopped the calls. Case files cover disbursal-API takeover at two Mumbai NBFCs, a vendor-hosted SaaS leak at a small finance bank, and ransomware at an NBFC group's overseas arms. They also cover a bank's dark-web exposure of 3,897 accounts, a ₹12.84 Cr mule-network drain and a ₹3.3 Cr banking-API drain in 87 minutes. The report flags Linux kernel privilege escalation in KEV (CVE-2026-46300, CVE-2026-53362) and RBI's six-hour incident reporting window. Controls: secrets inventory and vaulting, rotation, IP allow-listing and transaction limits on payout APIs, maker-checker on beneficiaries, same-day reconciliation, isolation of non-production and immutable backups.
Key points
- One leaked API secret drained more than ₹30 crore in minutes, with no malware, phishing or stolen password.
- Payment, payout, banking, cloud, KYC and bureau keys each act as a master password for a business workflow. Treat each as a privileged identity.
- In the next 24 hours, inventory every live key with a named owner and rotate any key that touched an app, repo or chat.
- Lock money-movement APIs to known addresses with hard limits, and alert on payout velocity and new beneficiaries.
- Ten board-level risks, each with an Indian incident from June to November 2026, from partner access and ransomware to mule fraud and compliance gaps.
- A 24-point resilience checklist covers governance, identity, secrets and payments, DPDP, third parties, detection and recovery.
CVE ids covered: CVE-2026-46300, CVE-2026-53362
The full report is a PDF that opens with a work email.