Package of Problems: How a Frontend NPM Library Leaked Internal API Keys
在安装新NPM包后应用变得不安全,在调试时意外发现内部API密钥并揭露严重漏洞。 2025-8-4 04:43:54 Author: infosecwriteups.com(查看原文) 阅读量:14 收藏

Iski

Free Link 🎈

Hey there!😁

Zoom image will be displayed

Image by AI

You know that feeling when you install a new NPM package and think, “Wow, my app is about to be 10% cooler”? Yeah, turns out it was also 100% more compromised. 😅

I was casually debugging a UI issue and ended up finding enough internal API keys to start my own fake startup. Not even kidding. So here’s how I discovered a $erious vuln sitting quietly in a package — gift-wrapped and ready to pwn.

Like every bug bounty hunter with trust issues, I was reconning public assets of a mid-sized SaaS company. The front-end looked like a React lover’s dream. Clean, snappy, and full of juicy third-party packages.

Using my favorite mass recon workflow:

subfinder -d target.com | httpx -mc 200 -title

I landed on a staging site:

staging.target-assets-cdn.com

文章来源: https://infosecwriteups.com/package-of-problems-how-a-frontend-npm-library-leaked-internal-api-keys-423784602d54?source=rss----7b722bfd1b8d---4
如有侵权请联系:admin#unsafe.sh