OOmnistu

Blog / Security

Security

The CreditNirvana exposure: two login flaws, 6.6 million collections accounts and 315,000 call recordings, and what they teach about AI call-center software

An independent researcher's account of two login flaws at CreditNirvana, an AI debt-collection platform: a hardcoded API key in its AI call center and an unchecked identity token in its main platform, exposing 6.6 million accounts and 315,000 call recordings. What the write-up, CERT-In and WIRED say, and what they leave open.

OOmnistu
Reviewed 2026-11-19 · 5 min read

On 18 November 2026 an independent researcher, Eaton Zveare, published a write-up of two vulnerabilities in CreditNirvana, an India-based debt collection platform owned by Perfios that advertises AI-driven collections. WIRED covered it the same day. This guide sets out what the researcher says he found, how the two flaws worked at a high level, what the sources do not say, and the engineering lessons for teams building similar systems. Everything below is the researcher's, CERT-In's or WIRED's account. We did not test any system.

What was reported

How the two flaws worked, in outline

Two separate paths: the call center app trusted a sign-in done in the browser and used a fixed key embedded in its own code; the main platform asked the server for a session using only a username, without checking the identity token it was sent.

Original diagram by Omnistu, simplified from the researcher's description. Not his figure.

  1. Call center (High). According to the write-up, the web app handled sign-in in the browser with Amazon Cognito, but the token it received was not used for the data calls. Those calls relied on an API key hardcoded in client-side JavaScript. Anyone who read the page's code could find the key. The researcher says it gave access to the call recordings, post-call recommendations, AI agent management and campaign tools.
  2. Main platform (Critical). The write-up says the app used Keycloak for identity, but the platform's own login call accepted a username in the request body and did not check the identity token sent alongside it. Combined with an unauthenticated call that listed more than 10,000 users, this let him sign in as a high-level user. CERT-In's wording is that an unauthenticated attacker could "establish sessions as arbitrary users including administrative users".

Both are the same class of mistake: the server trusted something the user's browser supplied instead of verifying it on the server.

What the sources do not say

Lessons for teams building AI-driven call or messaging tools

These are our suggestions, not findings from the sources.

For people with loans in India

None of the sources tells individual borrowers to take a specific step, and they do not list who is affected. The three clients named by the researcher are Aditya Birla Capital Finance, BharatPe and International Asset Reconstruction Company. If you hold an account with one of them and want to know whether your data was involved, ask the lender directly. Standard precautions apply to anyone: be careful with calls or messages that quote account details, and check your credit report for items you do not recognize.

This guide was prepared with AI assistance and reviewed on 19 November 2026.

Sources