Cloakroom Would Not Have Prevented October's Four Credential Incidents, Author Finds
The author, who built the open-source tool Cloakroom, reviewed four October incidents that exposed developer and AI agent keys: LiteLLM 1.107.0 shipping a credential stealer, a worm in Tensorlake's npm package, a Railway internal breach, and OpenCode's hosted Console exposing stored provider keys. Mapping each attack step against the tool's behavior, the author found that Cloakroom would stop none of the theft steps, which read disk, servers, or CI directly. It would only partially affect upstream copies, such as a key committed through an agent or a token passing through tool output into model context. In a controlled test with 11 dummy secrets, Cloakroom kept all of them out of the model's input, session transcript, and git history, though the author notes the result reflects a narrow setup.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in