AI Debt-Collection Platform Leak Exposes 6.6M Accounts Security researcher Eaton Zveare disclosed two critical vulnerabilities in Credit Nirvana, the AI-powered debt-collection platform owned by Indian fintech Perfios, exposing roughly 6.6 million borrower accounts and about 315,000 recorded collection calls. An unauthenticated REST endpoint allowed sequential-ID enumeration of full borrower profiles, while a misconfigured S3-compatible bucket set to public-read exposed call archives under a predictable naming pattern. India's CERT-In classified both issues as critical, and the exposed data falls under India's Personal Data Protection Bill as sensitive personal data. In early November 2026, independent security researcher Eaton Zveare disclosed two high‑severity vulnerabilities in Credit Nirvana, the AI‑powered debt‑collection platform owned by Indian fintech firm Perfios. The flaws granted unauthenticated access to 6.6 million borrower accounts and approximately 315,000 recorded phone calls from the platform’s agentic call centre. India’s Computer Emergency Response Team CERT‑In classified both issues as critical, prompting immediate public scrutiny and a rapid response from Perfios. Credit Nirvana markets itself as an autonomous decision‑engine that “reads a borrower’s full context, decides the next best action, and executes it autonomously, continuously, and within policy.” The platform is integrated into the collections pipelines of several of India’s largest fintech companies, handling millions of interactions each month. The breach therefore represents not only a massive data exposure but also a potential erosion of trust in AI‑driven financial services. 🔹 ---------- • Affected Component: ------------------- • Data Exposed: -------------- • Potential Exploitation: ------------------------ 🔹 Critical • Affected Component: REST API endpoint for borrower profile retrieval • Data Exposed: Personal identifiers, loan amounts, repayment history • Potential Exploitation: Unauthenticated GET requests could enumerate accounts and harvest PII 🔹 Critical • Affected Component: Internal call‑recording storage service S3‑compatible bucket • Data Exposed: 315 k audio recordings, timestamps, agent IDs • Potential Exploitation: Misconfigured bucket permissions allowed public read access The first vulnerability stemmed from an improperly scoped authentication middleware. The /v1 /v1/borrower/{id} endpoint was left without any token verification, allowing anyone who could guess or enumerate numeric IDs to retrieve full borrower profiles. The route accepted a simple integer identifier and returned a JSON payload containing the borrower’s name, PAN number, Aadhaar‑linked phone, email address, loan amount, outstanding balance, repayment schedule, and even the internal risk score used by the AI engine to prioritize collection actions. Because the IDs were sequential and started at 1, an attacker could script a rapid scan that harvested millions of records in under an hour. The flaw was compounded by a secondary issue in the pagination logic: the API ignored the limit parameter and defaulted to a maximum of 10,000 records per request, but the offset parameter could be set to any integer. By iterating the offset in steps of 10,000, the researcher demonstrated how the entire dataset could be exfiltrated with just a few hundred HTTP calls. The second vulnerability involved the storage layer for voice recordings. Credit Nirvana archives every outbound and inbound collection call in an S3‑compatible object store, tagging each file with metadata such as call id , borrower id , agent id , and timestamps. The bucket’s ACL Access Control List was mistakenly set to public-read , meaning any URL pointing to an object could be accessed without authentication. The researcher discovered that the bucket’s naming convention followed a predictable pattern: cn-call-recordings-prod-