🤖 AI Summary
This study addresses the widespread leakage of Large Language Model (LLM) API credentials in iOS applications, which has led to unauthorized access and financial losses for developers, yet remains underexplored in prior research. The authors present the first empirical analysis by constructing a high-quality dataset of 444 iOS apps and introducing LLMKeyLens, a dynamic analysis framework that detects leaked credentials without requiring source code or decryption. Leveraging network traffic interception, provider-specific key extraction, validity verification, and JWT parsing, the framework identifies exploitable credentials in 282 apps across at least ten service providers. Follow-up assessments reveal that only 28% of affected apps remediated the issue within three months, highlighting a significant gap between security best practices and real-world integration. The paper further uncovers three prevalent leakage patterns and calls for coordinated efforts among developer awareness, platform policies, and provider guidance to mitigate this critical vulnerability.
📝 Abstract
The rapid integration of large language models (LLMs) into mobile applications has introduced a new class of credential security risk: leaked credentials that grant unauthorized access to LLM inference services, causing financial damage to developers. Prior work on credential leakage has focused primarily on Android apps; to date, no empirical study has systematically investigated LLM API key leakage in iOS applications.
We present the first in-depth empirical study of API key leakage in LLM-integrated apps. We construct a high-quality dataset of 444 iOS applications, filtered from 1092 candidates through a standardized process, and develop LLMKeyLens, a dynamic analysis framework that detects LLM API key leakage via traffic interception, provider-specific key extraction, and active validity confirmation, requiring neither source code access nor binary decryption. Our analysis reveals that 282 applications expose exploitable LLM API credentials in network traffic, spanning at least ten providers. We identify three leakage patterns: JWT-based token leakage (48%), unauthenticated backend proxy access (33%), and plaintext API key transmission (19%). To assess remediation, we re-analyzed the same 282 vulnerable applications three months after responsible disclosure; only 28% had remediated the reported vulnerability, while 72% remained exploitable, with persistent issues stemming from unauthenticated backends and broken JWT implementations.
Our findings show that LLM API key leakage is both prevalent and persistent in the iOS ecosystem, exposing a systemic gap between developer practice and secure integration principles, and suggest that secure LLM integration requires not only developer awareness but also explicit security guidance from providers and platform-level enforcement.