Together AI Discloses Prompt Leak After AI Coding Agent Exposed Credential

Original title: Together.ai: Prompt Leakage for Requests
71AI Score

Together AI disclosed a security incident in which an AI coding agent committed a credential to its public GitHub repository xorl, granting access to a private Hugging Face repo holding prompt samples from MiniMax M3, GLM-5.2 and Kimi K2.6 requests in June and July 2026. An unauthorized party downloaded the samples and searched them for further credentials. The incident highlights supply-chain risk from AI agents in development workflows; Together advises customers handling sensitive prompts to enable zero data retention.

Full Report

Contents4 sections

We are notifying customers about a security incident involving a subset of prompts submitted to Together AI’s serverless inference service in June and July 2026. An unauthorized party downloaded stored prompt samples after a credential for a private repository was exposed in a public code repository.

We apologize for this incident. We are reviewing the affected data to determine what information was exposed and which customers require direct notification.

What happened

As part of routine software testing, we collected prompt samples authorized for that use and stored them in a private Hugging Face repository. The samples came from requests to the MiniMax M3, GLM-5.2, and Kimi K2.6 models, primarily on June 24, July 4, July 8, and July 14, 2026.

During development of our public GitHub repository, xorl, an AI coding agent committed a credential that provided access to the private Hugging Face repository. Our automated scanning detected the exposed credential, and we reverted the commit.

During the exposure window, an unauthorized party obtained the credential and used it to download the stored prompt samples. The party subsequently searched those samples for credentials to other services and tested whether those credentials were valid. Five of the credentials tested were canary credentials associated with a Dragos security experiment.

We have no reason to believe the unauthorized party has leaked this data further and understand that it has now been deleted.

Investigation and scope

We have worked with an external forensic investigation firm and law enforcement to investigate the incident.

Based on our review, we have not identified evidence of additional prompt leakage beyond this incident. Our review of the affected prompt contents is ongoing to determine whether sensitive personal information or other customer data was exposed. We will contact affected customers directly as needed with the findings relevant to them.

Changes we have made

Following the incident, we strengthened controls around development workflows, credentials, and customer data. These changes include:

  1. Using scoped or short-lived credentials, and keyless access where supported, to reduce the potential impact of credential exposure.
  2. Checking all pull requests for credentials.
  3. Making zero data retention (ZDR) the default setting for new accounts.
  4. Updating our development processes governing the use of AI coding agents.

What customers can do

Customers handling sensitive prompt data should enable ZDR in their account settings.

If you have questions about this incident or its potential impact on your organization, contact [email protected].