
The prompt leak that five decoys helped expose
Five of the credentials an outsider tried were decoys. They belonged to a Dragos security experiment, not to five customers whose accounts had been emptied. Even so, something had happened that a customer reading an AI service’s settings could not have seen: somebody outside the service had obtained stored examples of what people had sent it. In its November 21 notice, Together AI says the samples came from a subset of June and July requests to three models on its serverless service. The company says it had permission to keep samples for testing. A coding agent exposed a credential; the company detected the exposure, but not before an unauthorized party used it to download the collection. Permission to test the software was not permission for that party to read the samples. The useful distinction is between the customer conversation and the copy engineers keep to check their work. A team can secure the first and still mishandle the second. Together says it has changed how development credentials are scoped and made zero retention the default for new accounts. Customers with existing accounts should check their own settings rather than assume the new default applies. The company was still reviewing what the samples contained. Neither it nor the independent canary experiment supplies a count of people whose personal information was exposed.




