TL;DR: LLM-enabled iOS apps can expose reusable API credentials even behind proxies or obfuscation, according to Approov research, because static secrets remain extractable from client code and traffic. Mobile AI access needs short-lived credentials and runtime trust checks, or the same leaks can persist for months.
Editorial analysis by NHI Mgmt Group, based on content published by Approov: “The Hidden Vulnerability in the AI Apps: Why "Zero Secrets" Architecture is Essential”.
By the numbers:
- 64% of 444 iOS applications with confirmed LLM functionality exposed exploitable LLM API credentials in network traffic.
- Only 28% of the applications had successfully remediated the vulnerability three months later.
Key questions
Q: Why do backend proxies still fail to protect LLM credentials in apps?
A: A proxy only helps if the app-to-proxy trust step is strong.
Q: How should security teams handle exposed secrets in AI-driven environments?
A: Security teams should treat exposed secrets as active access paths and respond as though misuse can begin immediately.
Q: What breaks when mobile apps still store reusable API keys or tokens on the client?
A: The control fails because the client no longer owns a trustworthy execution environment.
Practitioner guidance
- Remove durable secrets from mobile clients Replace embedded API keys and reusable tokens with short-lived, conditionally issued credentials that are never stored in the app package.
- Enforce app and device attestation before issuance Require runtime proof that the app is genuine and the device is uncompromised before any backend or LLM credential is delivered.
- Audit proxy-based AI integrations for weak client trust Review backend proxy patterns for static tokens, unauthenticated calls, and replayable session secrets that let attackers bypass the intended separation.
Bottom line: LLM-enabled mobile apps can expose reusable credentials even when developers believe a proxy or obfuscation layer is enough to protect them.
Glossary terms: Zero-Secrets Architecture, Runtime Attestation, Certificate Pinning, Secrets Leakage
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Mobile AI access is becoming an NHI governance problem, not just an app security problem. Once a mobile client carries a reusable API key or token for an LLM service, that secret functions as a non-human identity credential with all the lifecycle burdens that implies. The issue is not simply whether the code is obfuscated but whether the credential can be discovered, replayed, and governed across issuance, use, and revocation. Practitioners should treat mobile AI integrations as part of the NHI estate, not as isolated app logic.
A few things that frame the scale:
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to the State of Secrets in AppSec.
- 54% of ransomware victims had credentials exposed before the attack, according to Verizon's 2025 Data Breach Investigations Report.
A question worth separating out:
Q: Should organisations use certificate pinning instead of secret rotation for mobile AI access?
A: No. Certificate pinning and secret rotation solve different problems. Pinning protects the transport path from interception, while rotation reduces the lifetime of a leaked secret. For mobile AI access, both are useful, but neither is enough on its own if the app still contains a reusable credential that can be extracted and replayed.
👉 Read our full editorial: LLM API credential leakage in iOS apps exposes mobile AI risk