Comet's 29 internal AI provider API keys compromised through Opik flaw
- Status
- Open
- Disclosed
- Data exposed
- 29 Comet API keys for OpenAI and Anthropic stored in Opik test workspaces
- Outage
- Opik on comet.com, about two hours on October 26, 2026
TL;DR: Comet, which provides a model evaluation platform for AI developers, says a threat actor gained unauthorized access to its Opik test workspaces and 29 internal AI provider keys. Comet revoked all 29 keys and says no customer data or accounts were accessed.
If you were affected
Comet deployed a fix to Opik on comet.com and to dedicated deployments managed by Comet, so users of those deployments need to take no action. Comet asks teams that run self-hosted or open-source Opik to:
- Upgrade self-hosted or open-source Opik to the latest version.
What happened
The threat actor gained unauthorized access to Comet's internal Opik test workspaces on comet.com between October 24 and 26, 2026, using a user API key from an inactive account. Comet says the account had no admin rights and it has no evidence that Comet's systems were involved in how the threat actor obtained the key. The threat actor exploited a flaw in Opik's AI provider settings to gain unauthorized access to 29 internal API keys and tried to reach other Comet systems with the flaw.
The 29 exposed keys were API keys for OpenAI and Anthropic that Comet stored in its own Opik test workspaces. Comet says no customer data, accounts, or customer AI provider keys were accessed, and that self-hosted and open-source Opik deployments were not affected. Opik on comet.com was unavailable for about two hours on October 26, 2026 while Comet deployed a fix, and AI provider settings, the Playground, and Ollie were temporarily disabled.
Comet contained the intrusion on October 26, 2026 after an AI provider alerted Comet to unusual activity, blocking the exploited functionality that morning and then deploying a fix. Comet revoked all 29 exposed keys, removed the inactive account from every workspace, audited all workspaces for stale members, and rotated all internal credentials as a precaution. Comet reviewed the access logs for the affected workspaces and for every account the threat actor created.
Comet changed Opik to require the API key to be re-entered when a provider address changes and to restrict which addresses provider requests can reach. Comet added monitoring for provider settings changes and unusual outbound traffic.
Timeline
-
Reported by @Cometml on X
-
Opik on comet.com unavailable for about two hours while a fix was deployed
AI provider alerted Comet to unusual activity; intrusion contained and exploited functionality blocked
-
Threat actor began accessing Comet's internal test workspaces on comet.com with an inactive account's API key
Independent analysis you can act on, straight to your inbox.
Thanks. is on the list.
Sources
- Comet blog: Opik Security Incident: October 2026, by Nimrod Lahav, co-founder and CTOcomet.com, accessed Oct 27, 2026
- @Cometml on Xx.com, Oct 27, 2026
- @Cometml on Xx.com, Oct 27, 2026
- @Cometml on Xx.com, Oct 27, 2026