How AI API Keys Leak From Mobile Apps, and How to Stop It

Dan Haiem, CEO of AppMakers USA, explains how AI provider keys end up exposed in mobile apps and what a secure setup looks like. The piece opens with a Wake Forest University study of 444 iPhone AI chatbot apps, 282 of which exposed paid AI access through their network traffic—researchers simply watched what apps sent over the network and collected credentials as they passed, letting anyone run AI requests on the developer's account. Worse, when the researchers warned all 282 developers and waited three months, only 28% had clearly fixed the problem. Haiem attributes the problem to speed to launch (calling the AI provider directly from the app skips building a backend), AI-generated code that ships unreviewed with keys in config files, prototypes quietly becoming production apps, and the false belief that a compiled app hides its secrets. The study sorted leaks into three patterns: replayable tokens (136 apps—tokens that leak and stay valid far too long, one expiring in 2125 and another still working after 128 days), no key needed (92 apps routing through unauthenticated servers that answer anyone), and plaintext keys (54 apps, 28 of which also exposed the hidden system prompt). Stolen credentials feed LLMjacking, with Sysdig estimating a worst case of over $46,000 a day in AI charges; other costs include copied system prompts, abuse under your account, provider suspension, and lost user trust. Haiem notes that deleting a leaked key isn't enough—many developers never revoke it. The recommended architecture: route every AI call through your own backend with the key in server-side secret storage, authenticate every request, keep tokens short-lived and user-bound, set rate limits and spending caps, monitor for unusual usage, keep the system prompt server-side, and rotate and revoke any key that ever shipped. He closes with an eight-item pre-launch checklist and the simplest test: install your own app, watch its traffic with a free proxy, and see what you can grab. 

https://shattered.io/ai-api-keys-leak-mobile-apps/

Comments

Post a Comment

Popular posts from this blog

OWASP ASVS 5.0 Released - Key Updates and What You Need to Know

The OWASP Foundation has released version 5.0 of the Application Security Verification Standard (ASVS), a major update to their security framework for web applications. This new version features restructured security requirements for better clarity, expanded guidance for cloud and API security, improved DevSecOps integration for CI/CD pipelines, updated threat modeling support, and enhanced compliance mapping with standards like NIST and PCI DSS. ASVS serves as a critical benchmark for developers building secure applications, penetration testers conducting security assessments, and auditors performing compliance reviews.  The standard is available for download from the OWASP ASVS project page, with organizations encouraged to integrate it into their software development lifecycles through code reviews and security testing tools. As a vendor-neutral, community-driven project, OWASP continues to welcome contributions to further develop the standard. This release represents an importa...
Read more

Critical OpenSSH Flaws Enable MITM and DoS Attacks

On February 18, 2025, HackRead reported on two critical vulnerabilities in OpenSSH, identified by the Qualys Threat Research Unit (TRU). The first vulnerability, CVE-2025-26465, affects the OpenSSH client and permits machine-in-the-middle attacks, potentially allowing attackers to impersonate legitimate servers and compromise SSH session integrity. This flaw exists regardless of the 'VerifyHostKeyDNS' setting and has been present since OpenSSH version 6.8p1. The second vulnerability, CVE-2025-26466, impacts both the client and server, enabling pre-authentication denial-of-service attacks that consume excessive system resources, leading to potential outages. Introduced in version 9.5p1, this issue persists up to version 9.9p1. Users are strongly advised to upgrade to OpenSSH version 9.9p2 to mitigate these vulnerabilities.  https://hackread.com/critical-openssh-flaws-expose-users-mitm-dos-attacks/
Read more

MITRE ATT&CK v19 Redefines How Defenders Model Modern Threats

MITRE ATT&CK v19 introduces one of the framework’s most significant structural changes in years, splitting the former Defense Evasion tactic into two clearer categories: Stealth and Defense Impairment. The release also expands coverage for AI-enabled adversary behavior, social engineering, and mobile detection strategies, while adding greater precision to ICS through new sub-techniques. Beyond taxonomy updates, v19 signals a broader evolution of threat modeling—toward more actionable, behavior-driven intelligence that reflects how attackers increasingly blend automation, deception, and cross-domain operations.  https://medium.com/mitre-attack/attack-v19-ff329cb65d66
Read more