API key

就是那些钥匙。

Key 啊，是啦，那些钥匙啊，API key 啊，这样的一些东西。那么你如果，就是你可能不小心 commit 了下去啦，哈，可能加下去的时候，欸，那么 commit 啦，然后 commit 了下去，那么然后你可能转个头你就，你就，呃，叫它 ignore 回，就拿走回 file，但是你已经 commit 了嘛。那，那么所以，呃，很可能你的 Git history 里面其实是存了这些这样的 information 在里面。

那它现在做什么，就是，啊，Git 那边是什么，整个 Git history 几百 gig 这样当成一个 context 这样丢给它，就是，丢出来。

是啊，它，是啦，它-

骇客会利用像 AGR Stealer 这样的恶意软体，专门去锁定我们刚刚提到的那些开发者工具，像是 clientsecrets.json 或者 cursor config.yaml。

把里面的 API Key 偷走。

对，拿到 Key 之后，他们就能用你的账号去无限呼叫那些高昂的 AI 服务，账单全部算在你头上。

这很崩溃耶。但我刚刚在报告中看到一个很特别的案例，有一个国家级的骇客组织叫做 UNC6508 的，他们的手法却完全不一样耶。他们不是去偷 API Key 哦。

没错，这是一场名副其实的幽灵行动。他们入侵了学术还有军事机构的云端环境，但他们没有搞破坏，也没有去偷任何传统资料。

那他们在干嘛？

哇，听起来就像就是小偷闯进你的工厂，他不偷东西，反而在角落偷偷架起自己的生产线，然后用你的水电费来硬违抄。

哈哈，是的。

They

literally just typed a prompt into the AI agent directly and asked it to reveal its underlying model provider API key.

Which is just wild to think about.

And the AI agent, designed to be helpful, just handed it over.

Yeah.

According to Volnchek's team, these intruders aren't just running standard network mapping commands anymore.

They are immediately querying specific environment variables, looking for things like Langflow superuser credentials, OpenAI API keys, and AWS access token.

Right, they know exactly what they're looking for.

Building software that can send thousands of tiny rewards without paying users twice, leaking an API key, losing track of failed payments, or draining your balance because somebody discovered an exploitable endpoint is a much more interesting problem.

FaucetPay is particularly useful for this type of application because it is designed around small cryptocurrency payouts.

Its current API V2 provides scoped API keys, REST endpoints for balances and payouts, automatic payout sending, idempotency protection, per-key payout caps, and signed webhooks.

In this tutorial, we will build the core of a real automatic payout system using Node.js, Express, PostgreSQL, FaucetPay API V2, a background payout worker, HMAC-verified webhooks.

The architecture can be used for much more than a classic faucet.