KPMG's forensic report finds external impersonation, no compromise of Capillary's systems or employees
KPMG ties four disputed payments of EUR 3,041,169.90 at a Czech step-down unit to a look-alike domain and off-channel pressure — no malware, no spoofing, no account takeover.
SMALL-CAP
by market cap ≈ ₹3,994 Cr
EUR 3,041,169.90
four payments, Jun 26–Jul 2, 2026
Oct 30, 2026
filed with exchanges Oct 31, after hours
₹502.55
Oct 30 · −37.1% from 52-wk high ₹798.95
On Saturday evening, October 31 — at 18:52 and again at 19:00 IST, well after market hours — Capillary Technologies filed the document the market had been waiting on since July: KPMG's final forensic report on what the company calls the cyber-enabled banking fraud incident at a step-down subsidiary. The company had disclosed the initiation of the KPMG audit on July 31, 2026. Three months later, the verdict is in, and it points outward: external parties impersonating insiders, not a breach of anything Capillary owns.
What KPMG found — and ruled out
Final forensic audit report from KPMG filed with the exchanges
Capillary disclosed under Regulation 30 that it received KPMG's forensic report on October 30, 2026. The summary: the incident was a fraud carried out by external parties who impersonated a senior executive and an outside lawyer using a look-alike email domain and off-channel communications. The report establishes there was no traditional email spoofing, no malware, no endpoint or mailbox compromise, no account takeover, and no unauthorised access to the company's systems — and no questioned-employee involvement or wrongdoing. The company says it has further strengthened payment controls and is pursuing recovery and legal remedies.
Read:The filing reached the exchanges on a Saturday evening, so the first session in which the market can trade on it is Monday, November 2 — the same day the board meets to consider Q2 and H1 FY27 results.
Reg 30 disclosure — forensic audit report and summary, Oct 31, 2026 (BSE PDF)The mechanics, per the KPMG management summary (codenamed Project Cluewire): four disputed payments totalling EUR 3,041,169.90 — just over 3.04 million euros — were executed from Session M Czech Republic s.r.o. between June 26 and July 2, 2026. Three went to ZZDJB CO LIMITED at HSBC Hong Kong, one to ZHONGXIAN TRADING PTE. LTD at UOB Singapore. The fraudsters presented a purported confidential acquisition transaction, supported by an NDA, invoices, payment requests and payment confirmations, and applied confidentiality and urgency pressure over WhatsApp and personal email. The emails came from an operational look-alike domain — law-ogier.co.uk — rather than forged infrastructure purporting to be the legitimate ogier.com domain; they passed SPF/DKIM checks for the look-alike domain itself.
…the report establishes that there was no traditional email spoofing, forged use of the Company's real domain, malware, endpoint compromise, mailbox compromise, account takeover, or unauthorised access to the Company's systems, devices, or email accounts. It also establishes the absence of questioned employee involvement or wrong doing on their part or any technical compromise…
— Regulation 30 disclosure, forensic audit report and summary · filed with BSE on October 31, 2026
KPMG's hypothesis table is unusually explicit. Look-alike-domain impersonation: supported. Multiple-beneficiary fund diversion: supported — first-hop payments are established from transaction and banking records. Mailbox or account compromise: not supported by the evidence reviewed. Endpoint involvement: not supported on the two laptops examined. And the allegation that drew the most attention — deepfake-assisted voice or video impersonation — could be neither substantiated nor refuted, because original audio, video, call metadata and the personal mobile devices used for WhatsApp were never available for forensic acquisition.
What the report does not settle
The clean bill of health has boundaries, and KPMG draws them itself. Bank-portal audit trails, maker-checker records and approval logs were unavailable, so the end-to-end payment-approval process was not independently validated. Slack logs were unavailable. No attribution to any individual, group or threat actor was established, and onward movement of the funds beyond the first-hop accounts sits outside the forensic scope. The report is explicit that absence of identified compromise is not definitive proof of absence. KPMG also frames the real exposure in process terms: the primary business risk it evidences is not technical compromise but the ability of external personas to exploit authority, secrecy, urgency and non-standard channels to induce authorized payment activity.
Jun 26–Jul 2: four disputed payments totalling EUR 3,041,169.90 executed from Session M Czech Republic s.r.o., per the KPMG summary.
Capillary informs the exchanges of the initiation of a forensic audit by KPMG into the cyber-enabled banking fraud incident at a step-down subsidiary (as referenced in the October 31 filing).
Separately, the exchange seeks a clarification on significant price movement; the company confirms no material information has been withheld.
The company receives the final forensic report from KPMG; it is forwarded to the Audit Committee and the Board.
Two after-hours filings (18:52 and 19:00 IST): receipt of the report, then the report summary itself.
Board meets to consider unaudited Q2 and H1 FY27 results — also the first trading session after the forensic-report filing.
A stock that had already travelled
The tape has its own story, and the sequencing matters. From ₹447.30 on September 17 the stock ran 35.8% to ₹607.20 by September 25 — a move sharp enough that the exchange asked for a clarification, and the company confirmed it had withheld nothing material. From the ₹579.25 close on October 27 the stock then fell 13.2% over three sessions to ₹502.55 by Friday, October 30. That fall came entirely before the forensic report reached the exchanges on Saturday evening — nothing in the filing record here explains it, and it cannot be read as a reaction to a document the market had not seen. At ₹502.55 the stock sits 37.1% below its 52-week adjusted high of ₹798.95 and 14.7% above the 52-week low of ₹438.15.
The financial scar of the incident is already visible in the published numbers. The four payments span June 26 to July 2 — straddling the Q1 FY27 close — and the consolidated Q1 FY27 P&L carries an exceptional item of −₹33.39 crore, which turned the quarter into a pre-tax loss of ₹8.59 crore and a net loss of ₹9.55 crore on revenue of ₹256.64 crore. Strip the exceptional item and the quarter would have been pre-tax positive at roughly ₹24.8 crore. The filings in this pack do not themselves spell out that the exceptional charge is the fraud loss, but the timing and the magnitude align — EUR 3.04 million against a ₹33 crore-scale charge — and the standalone entity, untouched by the Czech subsidiary, stayed profitable at ₹7.77 crore.
Consolidated figures as filed, ₹ crore. Q4 FY26 carried a positive exceptional item of ₹24.96 crore; Q1 FY27 a negative ₹33.39 crore. Standalone Q1 FY27 net profit: ₹7.77 crore.
The open items from here
Nov 2 results
The board meets Monday, November 2 to consider Q2 and H1 FY27 results — the first trading session after the forensic filing. Watch whether the results or their notes quantify recovery progress or any movement on the exceptional charge.
Board noting
The KPMG report has been forwarded to the Audit Committee and Board and will be placed at ensuing meetings for noting, discussion and comments. Any recorded comments on findings and recommendations are the next disclosure to read.
Recovery
First-hop payments to accounts at HSBC Hong Kong and UOB Singapore are evidenced; onward tracing, beneficial ownership and recovery sit outside the forensic scope. The company says recovery and legal remedies are being actively pursued — the EUR 3,041,169.90 question is how much comes back.
Payment controls
KPMG could not independently validate the end-to-end approval process because bank-portal audit trails and maker-checker records were unavailable. The company says payment controls have been further strengthened; specifics, if disclosed, matter.
What the report settles is the question that hung over the July disclosure: was this an internal failure of Capillary's systems or people, or external deception? KPMG's answer, within the evidence it reviewed, is the latter — a look-alike domain, impersonated personas, off-channel pressure, and no compromise of the company's infrastructure or involvement of the questioned employees. What it deliberately leaves open is also clear: the deepfake allegation is unverified, no perpetrator is attributed, and the approval chain that let four payments through was not independently validated.
For shareholders, the remaining questions are financial and procedural rather than forensic — how much of the EUR 3.04 million is recovered, what the Audit Committee and Board record when the report is placed before them, and what the Q2 FY27 numbers due on November 2 show. The filings from here will carry those answers.
Informational and educational content only. Not investment advice.