Three NBFCs in Telangana have reportedly suffered 304 fraudulent transactions involving approximately ₹18.14 crore between 19 October and 6 November 2026. The incidents raise serious questions about API security, digital loan disbursement controls, real-time transaction monitoring and cyber resilience.
According to a Times of India investigation published on 14 November 2026, attackers exploited payout-related technology to divert funds from financial institutions into multiple beneficiary accounts. Similar incidents have been reported in Karnataka, Maharashtra, Delhi, Chandigarh, Tamil Nadu and Puducherry.
The developments are particularly significant because the Indian Computer Emergency Response Team (CERT-In) had already issued a critical advisory on 9 October 2026 warning about attacks on payment and disbursement Application Programming Interfaces (APIs).
On 4 November, CERT-In issued a further critical advisory identifying an AI-assisted threat actor designated CRAFTY FALCON and warning that the campaign remained active.
1. Incident Snapshot: Three NBFCs, 304 Transactions
| Financial institution | Reported incident date | Transactions | Reported amount |
| VIVIFI India Finance | 19 October 2026 | 183 | ₹3.34 crore |
| Spandana Sphoorty Financial | 1 November 2026 | 82 | ₹7.80 crore |
| Keerthana Finserv | 6 November 2026 | 39 | Approximately ₹7 crore |
| Total | 19 Oct–6 Nov | 304 | ₹18.14 crore |
Figures are based on the 14 November Times of India report. The combined amount is calculated from the three reported figures; final verified losses and recoveries may differ.
Reported transaction distribution
Number of allegedly fraudulent transactions reported for each NBFC
050100150200VIVIFISpandanaKeerthana
The VIVIFI incident reportedly involved 183 transactions within approximately 88 minutes, equivalent to an average of one transaction every 29 seconds.
Investigators also reported that funds were routed through numerous bank accounts before reaching gaming and betting platforms. Although beneficiary accounts in Bengaluru appeared in all three investigations, no common accounts or IP addresses were identified across the three cases in the published findings.
Important distinction: Similar attack methods do not establish that all three incidents were committed by the same individuals or that each institution experienced identical technical control failures.
2. How Hackers Exploit NBFC Payout APIs
An Application Programming Interface (API) allows a lender’s technology platform to communicate with its banking partner or payment service provider.
In a legitimate loan disbursement, the system should verify that the loan is approved, the beneficiary is authorised, the amount is correct and the payment instruction complies with applicable controls.
Normal loan disbursement process
Loan approved
Valid customer, sanction and loan reference
Independent payout validation
Beneficiary, amount, authorisation and limits checked
Bank payment API
Authenticated and authorised transfer
Verified beneficiary receives funds
Attack pattern described by CERT-In
Compromised application or credentials
Attacker obtains access to a trusted payment environment
Direct payout API invocation
Business-level loan and beneficiary checks bypassed
Unauthorised transfers
Funds routed to attacker-controlled accounts
Illustrative process based on CERT-In Advisory CIAD-2026-0046, not a forensic reconstruction of any specific NBFC incident.
The critical weakness in this attack pattern is that a technically authenticated API request may not represent a legitimately authorised business transaction.
CERT-In describes attackers stealing payment aggregator, gateway or partner-bank credentials and invoking disbursement interfaces from trusted infrastructure. This can bypass checks normally performed by the lender’s application, including loan sanction, Know Your Customer verification, beneficiary validation and transaction limits.
3. Why Are These Attacks Particularly Dangerous?
Trusted infrastructure can be misused
Traditional network controls often place substantial trust in approved servers, IP addresses and authenticated service accounts.
However, an attacker who compromises an approved server or obtains valid credentials may generate payment requests that appear to originate from legitimate infrastructure.
A trusted IP address must never be treated as sufficient proof that a payment is authorised.
Small transactions may precede major losses
Investigators reported the use of ₹1 test transfers to establish whether payment routes were operational before larger amounts were moved.
Such transactions are not inherently fraudulent. However, an unusual small-value payment followed by high-value disbursements to a newly added beneficiary should be assessed as a possible warning pattern.
Automated attacks compress response time
The reported 183 transactions in approximately 88 minutes illustrate how quickly financial exposure can accumulate.
Manual reconciliation performed only at the end of the business day may identify a discrepancy after funds have already moved through several beneficiary accounts.
Attackers can exploit non-production environments
CERT-In’s 4 November advisory describes attackers entering through exposed testing or staging environments and moving into production systems through shared credentials or network connections.
This makes separation of development, testing and production environments a critical control.
4. CERT-In’s CRAFTY FALCON Warning: AI-Assisted Cyberattacks
On 4 November 2026, CERT-In issued Advisory CIAD-2026-0058, an escalation of its earlier October warning.
The advisory identified CRAFTY FALCON as an AI-assisted financial threat actor targeting BFSI infrastructure.
CERT-In reported the use of publicly available AI-enabled offensive tools to automate reconnaissance, generate attack scripts, adapt techniques and execute attacks at high speed.
The advisory also highlighted the deliberate targeting of institutions during weekends, holidays and other periods of reduced security monitoring.
Most importantly, CERT-In warned that some affected entities had been targeted again after incomplete remediation.
This creates two important lessons for financial institutions.
First, cybersecurity remediation must be validated through technical testing rather than simply marking vulnerabilities as closed.
Second, security monitoring must remain effective outside normal business hours, particularly where automated systems can initiate significant financial transactions.
5. Early Warning Signals That Could Help Detect API-Based Fraud
The following indicators are relevant for NBFCs, banks, payment aggregators and digital lending platforms.
| Early warning signal | Risk implication |
| Small test payment followed by large transfers | Possible validation of a fraudulent payout route |
| Multiple disbursements within minutes | Automated transaction abuse |
| Payout without an approved loan reference | Bypass of business validation |
| New beneficiaries receiving unusually large amounts | Payment diversion |
| API requests outside expected operating patterns | Possible compromised service credentials |
| Transactions exceeding sanctioned amounts | Weakness in payment-stage controls |
| Unexpected production API calls from testing systems | Environment separation risk |
| Mismatch between lender and bank transaction records | Unauthorised or unrecorded payments |
These indicators are investigative triggers, not conclusive evidence of fraud.
6. What Should IT Auditors and Risk Teams Test?
A practical audit should verify not merely that security policies exist, but that critical payment controls cannot be bypassed.
| Audit area | Recommended testing | Evidence required |
| API authentication | Review service identities, token validity and credential rotation | API gateway logs, secrets inventory |
| Loan validation | Confirm that payouts require a valid approved loan | Sanction records, payment references |
| Beneficiary controls | Test account changes and beneficiary verification | Beneficiary master, approval logs |
| Transaction limits | Verify individual and cumulative limits at payment stage | API configurations, test results |
| Maker-checker | Test independence of approval for high-risk payments | Workflow logs, approval records |
| Environment segregation | Verify that testing systems cannot initiate live payouts | Network rules, access permissions |
| Fraud monitoring | Test alerts for transaction velocity and unusual beneficiaries | Monitoring rules, alert cases |
| Reconciliation | Match bank debits against authorised loan records | Bank statements, ledger, payout files |
| Incident response | Test API suspension and credential revocation | Incident playbooks, exercise reports |
For material incidents, auditors should consider full-population reconciliation rather than relying exclusively on samples.
7. Relevant RBI and CERT-In Requirements
The regulatory implications extend across cybersecurity, technology governance, outsourcing and incident reporting.
CERT-In Advisory CIAD-2026-0046, 9 October 2026: Recommends strengthening API authentication, beneficiary verification, payout limits, monitoring, reconciliation, logging and incident containment.
CERT-In Advisory CIAD-2026-0058, 4 November 2026: Warns of the continuing AI-assisted campaign and the need to address exposed systems, shared credentials, cloud-management abuse and incomplete remediation.
RBI Master Direction on Outsourcing of IT Services, 2023: Establishes risk-management expectations for covered regulated entities outsourcing IT services, including governance, due diligence, monitoring and accountability.
RBI Digital Lending Directions, 2025: Establishes requirements concerning digital lending arrangements, including the handling of loan disbursements and repayment flows, subject to applicable provisions.
Institutions should also assess their obligations under applicable RBI information technology, cybersecurity, fraud-risk and incident-reporting requirements. The precise directions depend on the regulated entity’s classification.
8. What Should NBFCs Do in the Next 30 Days?
Days 1–7: Secure payment access
Inventory all active payout APIs, identify privileged credentials, revoke unnecessary access and assess exposed testing environments.
Days 8–15: Validate transaction controls
Confirm that every payout is independently matched to an approved loan, authorised beneficiary and permitted amount. Test cumulative limits and exception handling.
Days 16–23: Strengthen detection and reconciliation
Deploy or refine transaction-velocity monitoring, new-beneficiary alerts, near-real-time bank reconciliation and after-hours escalation.
Days 24–30: Independently test effectiveness
Conduct targeted API security assessments, simulate unauthorised payout attempts and report critical gaps to senior management with assigned remediation owners.
These are suggested institutional priorities, not statutory implementation deadlines.
9. Five Questions Every CRO, CISO and Internal Audit Head Should Ask
- Can any API initiate a fund transfer without a corresponding approved loan and verified beneficiary?
- Are payment limits enforced independently at the final payment execution stage?
- Can a compromised application server or service credential initiate payouts without additional authorisation?
- How quickly would the institution detect and stop 50 suspicious disbursements occurring within 15 minutes?
- Has the institution independently verified that earlier API vulnerabilities and remediation findings are fully resolved?
These questions translate the recent incidents into concrete tests of governance and control effectiveness.
10. Capability Building: RMAI’s IT Risk & Technology Governance Programme
The recent attacks demonstrate why technology risk management cannot be confined to infrastructure security alone. Professionals must understand application controls, API dependencies, third-party technology risk, incident response, financial transaction controls and regulatory expectations.
The Risk Management Association of India (RMAI) offers the professional programme IT Risk & Technology Governance in Financial Institutions, through Smart Online Course.
The programme covers seven specialised modules:
- IT Risk & Technology Governance Fundamentals
- Governance Framework, Strategy & Regulatory Expectations
- IT Risk Assessment, Information Assets, Controls & Risk Reporting
- IT Operations, Change Management, Resilience & Business Continuity
- IT Outsourcing & Third-Party Technology Risk Management
- IT Audit, Compliance Monitoring & Technology Assurance
- Cloud, Digital Technology & AI Risk Governance
It also includes 20 practical implementation toolkits and templates, including an IT Risk Register, Technology Risk KRI Dashboard, RBI IT Governance Gap Assessment Checklist and IT General Controls Audit Toolkit.
Programme Fee: ₹8,499 per participant, including GST and the applicable BFSI SSC assessment fee.
Course Details and Enrolment: IT Risk & Technology Governance in Financial Institutions.
For institutional nominations: info@rmaindia.org
11. Conclusion: API Security Is Now a Financial Risk Management Priority
The 304 reported fraudulent transactions involving three Telangana-based NBFCs illustrate how weaknesses in payment infrastructure can translate into significant financial exposure within a short period.
The incidents also demonstrate why financial institutions must look beyond conventional perimeter security.
An institution may have firewalls, approved IP addresses, authenticated API credentials and established loan-processing procedures, yet remain exposed if payment execution is not independently linked to legitimate business authorisation.
The emerging threat is particularly concerning because attackers are reportedly using automation, compromised trusted infrastructure and AI-assisted tools to accelerate financial fraud.
The most important lesson is that every digital payout must be independently authenticated, authorised, validated, monitored and reconciled, regardless of whether the payment instruction originates from a trusted application or infrastructure.
For banks, NBFCs and fintechs, this is a combined responsibility of Technology, Information Security, Operational Risk, Fraud Risk, Compliance and Internal Audit.
The priority should be demonstrable control effectiveness, rapid detection and the ability to prevent unauthorised payment instructions from becoming actual financial losses.
Sources and References
- The Times of India, 14 November 2026: Inside the International Cyber Raids on India’s NBFCs
- CERT-In Advisory CIAD-2026-0046, 9 October 2026: Threat Actors Exploiting Payment and Disbursement APIs
- CERT-In: Current Security Advisories, including CIAD-2026-0058, 4 November 2026
- The Indian Express, 16 November 2026: 12 NBFCs Lose Over ₹65 Crore to Cyber Fraud in Delhi-NCR
- Moneycontrol, 10 October 2026: CERT-In Warns NBFCs and Fintechs of Payment API Attacks
Editorial note: Figures reflect publicly reported investigations as of 16 November 2026. Reported transaction counts, financial losses and suspected attack mechanisms remain subject to investigation and reconciliation. The audit and remediation recommendations are professional risk analysis and should not be interpreted as findings of negligence against any named institution.