📖 Glossary
AI Box (also known as Agent Computer / Agent PC), is a dedicated local hardware device that runs AI Agents. Pre-installed with an AI agent management system, plug-and-play, running 24/7. Users can remotely command AI to work via Discord, Slack, Telegram, WhatsApp, and more.
Summary: On the night of October 16, an attacker reached a legacy system OpenCode was already retiring, and third-party API keys stored in Console workspaces went with it. About 1.4% of Console users were emailed, and some woke up to four-figure charges. KAIHE AIBOX makes one point: a key you never handed to a workspace cannot be stolen from it. The KAIHE Password Vault ships with the device, Agents request a key before use, you approve it, and the approval carries limits on use count, expiry and endpoint scope.
What happened that night
An attacker reached a legacy system OpenCode was decommissioning. On the morning of the 17th, affected users were told that provider keys saved in their workspace may have been exposed, and to revoke, replace and review usage.
At 15:30 UTC, security researcher Matt Johansen posted a screenshot of the email on X. At 18:08, OpenCode confirmed a breach connected to a large scale distillation attack, affecting 1.4% of Console users.
The keys lived in Console workspaces, not the copies the CLI keeps locally; co-founder Dax Raad said keys used by the regular agent never reach company servers. Anthropic and Google revoked the keys they judged exposed, and OpenAI restored access and refunded consumed credits.
The 1.4% figure is the least useful part
The first reaction is relief that it was not you. Run the number the other way: if your key sat inside that 1.4%, it was 100% for you.
That is the structural problem with hosted credentials. Good platform security still only produces after-the-fact remedies. By the time the email lands, the keys have been gone for over a dozen hours. Notify, revoke and refund all operate downstream of the exposure, and none removes the usage history already recorded against your account.
The bill is not the worst layer
Identity comes first. A key belongs to an account, and the account carries a payment method, team seats and call history. What an attacker takes is not a string of characters but an identity that can act with your authority.
Data flows second. Every model call sends content to the provider, and whatever someone runs on your key is logged under your account. OpenCode tied this event to a large scale distillation attack, bulk collection of teacher-model output to train a student model, so if you were inside that 1.4%, that history has your name on it.
Opacity third. The company has not said how many exposed keys were used. You infer it from a usage curve in a provider dashboard.
The KAIHE AIBOX answer
One line: the key never leaves your local network.
KAIHE AIBOX is a dedicated Agent Computer shipping with the KAIHE Password Vault preinstalled. Passwords and API keys live in the vault, travel with the device, and are never uploaded to a cloud workspace. When an Agent needs a key it does not browse files. It searches the vault, locates what it needs, and asks you.
The request cannot be skipped. You see who is asking, which credential and what for, then you decide. Only after you approve does the vault hand over usage rights, and the grant carries boundaries:
- A use count: grant three calls and the grant dies when they are spent
- An expiry date: grant until midnight and it is revoked automatically
- An endpoint scope: allow one endpoint on one service and deny the rest
The three stack. An approval can read: this endpoint, today only, five uses. The Agent gets a limited grant, finishes the work, and it expires on its own. The key never leaves your LAN.
Two approaches, one table
| Dimension | Hosted on a platform | KAIHE Password Vault on KAIHE AIBOX |
|---|---|---|
| Where the key lives | Someone else's cloud workspace | A device on your own LAN |
| Who holds a working credential | The platform holds one alongside you | Nobody without your approval |
| Usage cap | Usually unavailable | Set a use count |
| Expiry | Usually unavailable | Set an expiry date |
| Endpoint scope | Usually not possible | Limit reachable endpoints |
| Recovery | Revoke, refund, rotate | Nothing was handed over |
Three things you can do today
Rotate now. Any long-lived key ever stored on a hosting platform should be revoked and reissued.
Constrain what you issue. A read-only key capped at fifty dollars and pinned to your egress IP is a fifty-dollar incident.
Move Agent credentials local. The more convenient the platform, the more you depend on it never failing, and whether it fails is not your decision.
So where does a key belong? Since October 17 that question has a concrete answer.
Related Reading: - Meta Muse vs KAIHE AIBOX: what is actually different - When your Meta Muse subscription ends, does your personal AI assistant data stay?
For more information, search [KAIHE AIBOX] or contact: [email protected]
KAIHE AIBOX · 7x24 Personal AI Assistant | Product Center