Loading story…
OpenAI confirmed that a security incident at Mixpanel, its third-party analytics provider, led to the exposure of limited identifiable information for some users of the OpenAI API product. The breach did not affect OpenAI's core infrastructure, ChatGPT, or other products, and no sensitive data such as passwords, API keys, payment details, or chat content was compromised. The exposed data included names, email addresses, approximate locations, operating system and browser details, referring websites, and organization or user IDs associated with API accounts. OpenAI responded by removing Mixpanel from its production environment and began notifying affected users and organizations directly.
Mixpanel attributed the breach to a smishing (SMS phishing) campaign detected on November 8, 2025, which allowed unauthorized access to a portion of its systems. The company took immediate action by securing affected accounts, revoking sessions, rotating credentials, blocking malicious IPs, and engaging external cybersecurity experts for remediation. Both OpenAI and Mixpanel emphasized that only a limited subset of customers was impacted, and users not directly contacted were unaffected. OpenAI continues to investigate the incident and has terminated its use of Mixpanel for analytics on its API frontend.
See attribution, scope, and your downstream exposure.
6 events from the most recent confirmed update back to the earliest known activity.
On November 27, 2025, Mixpanel published a public response describing the recent security incident and its remediation efforts. The statement formalized the company's acknowledgement of the breach and the steps taken to contain it.
In response to the incident, OpenAI removed or suspended Mixpanel from its production environments, began directly notifying affected users and organizations, and launched a review of third-party vendors. The company warned customers to watch for phishing and social engineering attempts using the exposed metadata.
On November 26, 2025, OpenAI disclosed that a breach at third-party analytics provider Mixpanel exposed limited data for a subset of API users. OpenAI said its own systems and products such as ChatGPT were not compromised.
After detecting the intrusion, Mixpanel took containment actions including securing affected accounts, blocking malicious IP addresses, resetting employee passwords, and engaging external security experts. The company also began investigating the scope and impact of the breach.
Following the compromise of Mixpanel, an attacker accessed and exported limited analytics metadata tied to some OpenAI API accounts. Exposed fields included names, email addresses, approximate locations, browser and OS details, referring websites, and organization or user IDs, but not API keys, passwords, chat logs, or payment data.
Mixpanel detected a smishing (SMS phishing) campaign on November 8, 2025, which led to unauthorized access within its environment. The incident later proved to affect customer data held for third-party clients including OpenAI.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See attribution, scope, and whether this vendor sits anywhere in your supply chain.
16 references tracked. Mallory keeps watching after this page renders.
scworld.com
Open sourcecio.com
Open sourcesecurityonline.info
Open sourcebankinfosecurity.com
Open sourcebleepingcomputer.com
Open sourcehackread.com
Open sourcemixpanel.com
Open sourcecsoonline.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
OpenAI experienced a supply chain attack that resulted in the exfiltration of some customer data, specifically affecting visitors to its API documentation. The breach was traced to a compromise of Mixpanel, a third-party analytics provider, which notified OpenAI of the incident after detecting the attack. OpenAI responded by discontinuing its use of Mixpanel and publicly acknowledged the breach, emphasizing that the damage was limited but still notable due to the nature of the supply chain vector. In response to the growing threat landscape, including the risk of adversaries leveraging AI models for cyberattacks, OpenAI has expanded its 'defense in depth' security strategy. This includes the formation of the Frontier Risk Council, composed of experienced cyber defenders, to advise on safeguarding AI capabilities and preventing their misuse. Additional measures include enhanced guardrails, external red team testing, and a trusted access program for customers, all aimed at strengthening the security posture of OpenAI's AI ecosystem and mitigating risks from both supply chain attacks and malicious use of AI technologies.
Jun 29, 2026
OpenAI patched a vulnerability in its macOS ChatGPT application that could have enabled attackers to obtain sensitive data. Public reporting did not identify the flaw’s root cause, affected releases, patch version, CVE, disclosure source, or evidence of exploitation, but the issue highlights the client application as a sensitive attack surface for organizations deploying AI tools. Separately, OpenAI said it banned accounts that used its models to support romance-scam operations, including victim outreach, translation, sustained engagement, and investment-fraud lures. The company described a three-stage process—“ping,” “zing,” and “sting”—and cited campaigns linked to Cambodia, U.S. medical professionals targeted through golf-related social-media engagement, and young men in Indonesia targeted through social-media advertisements.
Oct 2, 2026
Organizations are facing escalating security exposure from employee and developer use of public AI services without adequate controls. A viral social-media trend prompting ChatGPT to “create a caricature of me and my job based on everything you know about me” is being cited as a visible indicator of **shadow AI** and potential **data leakage**, because users may be sharing work context and sensitive details into non-sanctioned LLM accounts and then posting outputs publicly. The public sharing can also aid **social engineering** by revealing roles, access, and other targeting cues; if an attacker compromises an employee’s LLM account, they may be able to review prompt history for sensitive information. Separately, Cyble Research and Intelligence Labs (CRIL) reported widespread **credential mismanagement** involving OpenAI/ChatGPT API keys, identifying **5,000+ public GitHub repositories** with hardcoded credentials and roughly **3,000 production websites** exposing active keys in client-side assets (e.g., JavaScript). CRIL noted that secrets often persist in commit histories, forks, and archived projects, and that automated scanning/indexing can shrink the time from exposure to abuse to minutes—enabling unauthorized API usage, cost fraud, and potential downstream compromise where those keys are tied into broader application workflows.
Jun 29, 2026