LowVulnerabilityMonitoring

Reddit post says LiteLLM leaked key was deleted but not revoked

A Reddit post reports a LiteLLM key was deleted from a repo but not revoked; details are unconfirmed, so revoke any leaked key first.

Published
Exploitation
No evidence in the sources; the headline does not say the key was misused

What happened

According to a post on Reddit’s r/AskNetsec community, a key associated with LiteLLM was leaked, then deleted from the repository but never revoked. The post title asks how fast a leaked key should be killed Reddit: LiteLLM’s leaked key was deleted from the repo but never revoked, how fast do you kill a leaked key?.

Only the headline could be retrieved. The full post and any comments could not be reviewed. The following is not confirmed:

  • What kind of key it was and what it gave access to.
  • Whether the LiteLLM maintainers have confirmed the leak.
  • Whether the key was used by anyone else.
  • When the leak happened and whether the key has since been revoked.
  • Whether any independent outlet has covered the story.

No CVE, affected version or fix is named in the headline.

Am I affected?

Not confirmed. The headline does not identify affected LiteLLM versions, users or deployments, and it does not say that customer data or systems were exposed. Without the article, there is no basis to say that LiteLLM users are at risk.

What to do now

  1. Treat the Reddit post as an unverified claim and wait for confirmation from LiteLLM or another primary source before drawing conclusions about its impact.
  2. If you have committed any secret (API key, token, password) to a repository, revoke it at the issuing provider and issue a replacement. This is a general practice, not a fact drawn from the source.
  3. Check the provider’s access logs for the exposed key, if the provider offers them.

Sources