SecurityThreats & vulnerabilitiesNote
What Spandana Sphoorty’s 2 November filing says about ₹7.80 crore of unauthorised debits on 1 November, against its own half-year profit and the rules on reporting a cyber fraud.
Spandana Sphoorty Financial, a microfinance lender listed on the NSE and BSE, told the exchanges on 2 November that about ₹7.80 crore was debited from one of its bank accounts on 1 November without authorisation, in multiple transactions during the day, to 82 beneficiary accounts.1 Three days earlier it had reported a profit after tax of ₹30 crore for the six months to September.2 The filing calls it a “cyber fraud incident” and gives its nature as “unauthorised transactions through a cyber fraud, details under investigation”. It does not say how the transactions were made, and it names no one.1
₹7.80 crore
debited without authorisation on 1 November, to 82 beneficiary accounts
About 26% of Spandana’s profit for April to September, and 43% of the ₹18 crore it made in July to September, by our arithmetic.2
On finding the debits, by the company’s account:1
Still open: which bank, which services were stopped, whether any money has come back, and who was involved, which the annexure lists as “under investigation”. Spandana says it will tell the exchanges about recoveries and the outcome “as and when the inquiry progresses”.1
Our 1 November piece rested on unnamed sources: The Economic Times put losses at small NBFCs at about ₹300 crore in two months.7 Here a named, listed lender with assets under management of ₹5,364 crore2 gives its own figure. Its filing does not describe the attack, and we do not link it to those reports.
The RBI’s cybersecurity and fraud Directions of 31 July 2026 both put their reporting duties on every NBFC above the Base Layer and on Base Layer NBFCs with assets of ₹500 crore or more.35 Read together with CERT-In’s Directions and SEBI’s listing rules, a fraud like this one is reported four ways:
One cyber fraud, four sets of reports: the first are due six hours after it is found
Reporting duties for a listed NBFC after a cyber fraud, by rule and deadline, in force on 3 November 2026
Bank and the 1930 portal
Reversal and freezing requests to the bank; a complaint on the cybercrime portal. Spandana: both on 1 November.
RBI and CERT-In: 6 hours
Cyber incidents to the RBI on DAKSH “within six hours of detection”, and CERT-In told; CERT-In’s own clock is 6 hours from noticing.
Exchanges: 12 or 24 hours
Regulation 30: within 12 hours if the event arises inside the company, 24 if outside. Spandana filed on 2 November.
Police, then a fraud return
Fraud to the police “immediately”; a Fraud Monitoring Return to the RBI within 14 days of classifying it as fraud.
Source: RBI NBFC Directions (cybersecurity; fraud risk), 31 July 2026; CERT-In Directions, 28 April 2022; SEBI LODR Regulations (amended to 22 January 2026); Spandana Sphoorty filing, 2 November 2026 · as of 3 November 2026 · Spandana's filing confirms the bank and portal reports; it does not say which other reports have been made
The sources for each step: the RBI’s cybersecurity Direction, paragraphs 28 and 141, which also require the NBFC to “pro-actively notify” CERT-In;3 CERT-In’s Directions, whose Annexure I lists “Unauthorised access of IT systems/data” and “Attacks or incident affecting Digital Payment systems”;4 the RBI’s fraud Direction, paragraphs 40 and 43, whose list of fraud types includes “Fraudulent electronic banking / digital payment related transactions”;5 and SEBI’s Regulation 30(6). The same rules also put “details of cyber security incidents or breaches” into each quarter’s corporate governance report, under Regulation 27(2)(ba).6
Sources
Disclosure. TechBag is a software reseller: it earns a margin when a reader buys through it, including from vendors named here. The analysis is TechBag’s own; no vendor paid for or saw this piece before publication. Facts are labelled reported, TechBag count or our view.