Single API Key from a Chrome Extension Led to 5.2 Million Exposed Customer Records
文章描述了一个Chrome扩展的安全漏洞案例:该扩展因暴露不安全API和硬编码密钥导致潜在数据泄露风险。通过负责任的披露,问题得以及时解决,保护了数百万用户的数据安全。 2025-8-9 05:35:27 Author: infosecwriteups.com(查看原文) 阅读量:199 收藏

Erkan Kavas

Story of an IDOR with insecure API but responsible disclosure that saved millions of users data. (Lovely 5k$)

During one of my routine explorations of public Chrome extensions, I stumbled upon a chain-owned extension belonging to a popular Asian coffee delivery platform. The extension, designed for quick order access, included preconfigured API endpoints and a hardcoded authorization key.

Press enter or click to view image in full size

secret coffee chain in asia. @ spoonuniversity . com

Most developers assume Chrome extensions are harmless. But once installed, they’re just ZIP archives — any resource, including JavaScript and config files, is easily accessible.

According to Google’s Chrome Web Store Developer Program Policies, extensions must not expose sensitive credentials or grant unauthorized access to user data. This incident clearly violated those rules, and the extension was voluntarily taken down within days of the report.

Cases like this may also highlight why Google has been moving away from Chrome Apps entirely — the end of support for Chrome Apps has been gradually rolling out, with full deprecation planned across all platforms. You can read more about that in Google’s official announcement. 🥹


文章来源: https://infosecwriteups.com/single-api-key-from-a-chrome-extension-led-to-5-2-million-exposed-customer-records-0cc81545a7a8?source=rss----7b722bfd1b8d--bug_bounty
如有侵权请联系:admin#unsafe.sh