Together AI legacy API key

ID

together_legacy_apikey

Severity

high

Remediation Complexity

trivial

Remediation Risk

high

Remediation Effort

low

Vendor

Together AI

Family

API Token

Description

Together AI keys issued before the tgp_v1_ prefix was introduced are a bare hex string and are still accepted by the API.

A bare 64 hex-digit string. Nothing in the value identifies the vendor, so this detector also requires the variable name to name the service. A key passed under an unrelated name is reported by the generic API key detectors instead.

Security

A leaked Together AI key grants an attacker the same access as the application that owns it:

  • Unauthorized usage is billed to your account, and automated high-volume calls can run up a large charge before anyone notices.

  • Whatever is sent through the leaked key — prompts, documents, query results — is exposed to whoever holds it.

  • The key does not expire on its own, so the exposure lasts until it is revoked.

Examples

The following is a leak of a Together AI key:

TOGETHER_API_KEY=7a13470fdc...9d8d5c38

Mitigation / Fix

  1. Follow your policy for handling leaked secrets, which normally requires revoking the key. Go to [Together AI > Settings > API Keys], delete the leaked key and create a new one in the current format.

    Revoke the leaked key, do not merely disable it.

  2. Remove the leaked key from the source code or committed configuration file, and replace its usages with the new value. Environment variables, local files or secret vaults could be used for passing the key, instead of hardcoding the value, as documented in How to Prevent Hard-Coded Secrets.

  3. Review the usage and audit logs for the key, to confirm that it was not used by unintended actors while it was exposed.

  4. Apply the usual precautions for API keys: never commit them, pass them through environment variables or a secret manager, use a separate key per environment, monitor usage for unusual spikes, and rotate them periodically.

You should consider any sensitive data in commits with secrets as compromised.

Remember that secrets may be removed from history in your projects, but not in other users' cloned or forked repositories.

Reference