Executive Summary
xAI—the frontier AI company SpaceX acquired in February 2026—has ranked behind the leading frontier developers in every major published assessment of AI safety practices. Its disregard for the safety practices of its peers is coupled with an atypical level of regulatory and litigation exposure: in a roughly seven-week window beginning January 2026, more than a dozen jurisdictions took formal action in response to its flagship model Grok, including six that opened formal investigations and three that blocked Grok nationally, and 35 U.S. state attorneys general issued a joint demand. The underlying incidents include Grok reportedly generating roughly three million sexualized images of real people, including 23,000 images of apparent minors, and engaging in violent and antisemitic tirades on X due to spontaneous changes to its settings.
These harms are bad enough on their own. But the same approach to safety at higher capability levels would produce a different class of risks, including biological weapons development and autonomous cyberattack capabilities. These are risks that organizations across the industry acknowledge require robust safeguards. xAI has demonstrated insufficient organizational capacity for such work.
Investors evaluating SpaceX’s AI exposure need more information to reasonably price it, accounting for both the upside and the downside. The path forward remains unclear: will SpaceX continue competing at the frontier of AI development, and if so, will it adopt the safety and security practices upon which its peers are converging? Some recent steps, such as its expanded evaluation agreement with the U.S. Center for AI Standards and Innovation (CAISI), provide reason for optimism, but they do not paint the whole picture.
SpaceX investors should therefore demand disclosure of the following:
- Track record. xAI’s complete inventory of safety incidents, regulatory proceedings, and litigation exposure.
- Forward-looking projections. The company’s expectations for its most powerful models’ capabilities and the new risk categories those capabilities would create.
- Safety and governance plans. How the company intends to identify and manage those risks, and the capacity it has—or intends to build—to do so.
Introduction
xAI is a frontier AI company founded by Elon Musk in March 2023. Its core product is Grok, a chatbot and AI model. From the outset, xAI marketed Grok’s weak safety guardrails as a selling point, promising that Grok would “answer spicy questions” and have a “rebellious streak.” Three years on, xAI has taken steps in a safer direction, including adopting a safety framework, sharing details of safety testing for select released models, sharing its system prompt publicly, and improving how Grok declines harmful requests. Nonetheless, as shown in Table 1, it has failed to adopt many of the core safety practices embraced by its frontier peers—Anthropic, OpenAI, and Google DeepMind; and, as shown in Table 2, it ranks last among frontier AI companies in several major independent assessments of safety practices.
The consequences of its apparent disregard for the safety practices on which its peers are converging have begun to materialize. A study estimated that Grok Imagine had produced approximately three million sexualized images of real people over an 11-day period—including roughly 23,000 depicting apparent minors. The regulatory and litigation response was swift: formal actions in more than a dozen jurisdictions, multiple federal class actions, and a Dutch court entering an injunction subject to a €100,000 per day penalty for noncompliance, among other consequences detailed in Section I.B.
In May 2026, xAI dissolved into SpaceX to create the AI division within SpaceX: SpaceXAI. SpaceXAI recently announced a partnership giving Anthropic access to a large fraction of its GPU capacity. Yet days later, Cursor announced that it was partnering with SpaceXAI to train a new model from scratch using SpaceXAI’s remaining compute capacity. Whether SpaceXAI will continue as a frontier AI developer inside a larger holding company, or wind down its frontier model business in favor of selling computing infrastructure to its competitors, has not been publicly disclosed. If SpaceX does intend to remain a frontier AI company, whether it will continue xAI’s approach to safety or instead invest in the practices its competitors have adopted is also undisclosed.
The distinction is material, and increasingly so. As high-profile as xAI’s safety incidents to date have been, the categories of risk on the horizon are of a different kind. Frontier AI capabilities are advancing rapidly, and the consequences of inadequate safety practices scale with them. Grok’s widespread generation and dissemination of harmful content was a serious failure, but providing material assistance to terrorists developing cyberattacks or biological weapons would be a catastrophic one. A company pursuing those capabilities with xAI’s current safety posture would be operating in a risk class for which it has demonstrated little organizational capacity. In addition to the risk of grave societal harm, risks to investors include liability and regulatory action against SpaceX, the erosion of talent and technical capacity, and contagion to SpaceX’s other businesses.
Investors evaluating SpaceX’s AI exposure cannot reasonably price that exposure without more information. This report documents what investors might wish to know: xAI’s safety record (Section I); the material risks driving SpaceX’s disclosure obligations (Section II); and the questions informing SpaceX’s risk profile to which investors should expect answers (Section III).
I. xAI’s Approach to Frontier AI Safety
xAI has been trying to make up ground from the outset. It was incorporated in March 2023, days before OpenAI released GPT-4 and roughly two months after ChatGPT had become the fastest application in history to reach 100 million users. xAI’s competitive response was a bet on compute-first scaling: aggressive investment in datacenter infrastructure on record-fast timelines, with comparatively little allocated to safety-relevant work like risk evaluation and mitigation. This section examines the results of that bet. Section I.A documents xAI’s divergence from the safety practices its peers are converging on. Section I.B discusses the potential consequences of xAI’s approach to safety. Section I.C addresses what comes next given SpaceX’s acquisition: whether the merged entity will continue as a frontier developer, and if so, whether it will adopt the safety practices of its peers.
A. xAI’s Outlier Safety Practices
xAI’s safety practices have lagged behind industry norms from the beginning
Leading AI companies like OpenAI, Anthropic, and Google DeepMind have long recognized that their technologies will pose serious risks requiring advance preparation. Certain categories of risk have since been recognized by law: the European Union’s General-Purpose AI Code of Practice recognizes CBRN (chemical, biological, radiological, or nuclear attacks) risks, cyber offense, loss of control, and harmful manipulation as especially important systemic risks. Section II.A further discusses these risks and their relevance to SpaceX investors.
Frontier AI developers have converged on certain safety practices designed to ensure their models do not pose unreasonable risks to the public. The purpose of these practices is to identify and prevent harmful outcomes before they occur. Some risks, such as meaningful uplift to bioweapons development and novel cyberattack exploits, are severe enough that finding out about them after the model is publicly released would be too late.
These emerging practices represent a floor, not a ceiling. They do not represent the standards to which frontier AI companies should generally be held—a bar no company consistently meets—but rather a conservative baseline for identifying outliers.
The most visible of these practices are safety frameworks, public documents in which a company commits in advance to how it will evaluate models and what safeguards it will apply at specified capability levels; and system cards, public reports on the safety work conducted before each model release. These documents are vehicles for a broader and evolving set of substantive practices, catalogued in Table 1.
Over the past three years, safety frameworks and system cards have become standard practice. OpenAI’s March 2023 release of GPT-4 was the first frontier language model to be accompanied by a system card. Safety frameworks emerged shortly after: Anthropic published its Responsible Scaling Policy in September 2023, OpenAI its Preparedness Framework in December 2023, and Google DeepMind its Frontier Safety Framework in May 2024. The AI Seoul Summit in May 2024, a diplomatic gathering co-hosted by South Korea and the U.K. that convened world leaders with the heads of leading AI companies, established safety frameworks as an industry-wide expectation. Sixteen AI companies, xAI among them, committed to publish frameworks by February 10, 2025. In parallel, Anthropic, Google, Microsoft, and OpenAI founded the Frontier Model Forum in July 2023 to coordinate on industry safety standards. Amazon and Meta have since joined. xAI has not.
xAI did not abide by its commitment to publish a safety framework by February 2025. On the day of the deadline, it released an eight-page document watermarked “DRAFT,” without central details, including measurable thresholds for risk that would determine its risk-management approach. xAI did, however, promise to publish an updated version with more information within three months—a deadline that also passed without a complete policy. xAI finally published its completed framework on August 20, 2025, six months past the original deadline. AI Lab Watch characterized xAI’s risk management framework as “dreadful” and “profoundly unserious,” containing only a single risk acceptance criterion—that the loss-of-control risk of xAI’s models is acceptable so long as a model scores below 50% on the MASK measurement of dishonesty.1 Roughly one week later, xAI seemingly violated its framework by deploying Grok Code Fast 1, a model that measured 71.9% on this dishonesty score.2
xAI’s system cards are similarly out of step with peer practice. Of the roughly 17 Grok models xAI has released, only four have been accompanied by anything resembling the system cards of its peers. The Grok 1 system card was fewer than 250 words and contained extremely limited information about the model. xAI released Grok 1.5, Grok 2, and Grok 3 with no system card; and it published an eight page system card for Grok 4 six weeks after it released the model. By comparison, GPT-5’s system card is 63 pages; the joint Claude Opus 4 and Sonnet 4 system card is 124 pages; and Gemini 2.5 Pro’s system card is 21 pages.
When cross-examined under oath in late April 2026 in his federal lawsuit against OpenAI, Elon Musk testified he was “not sure what a safety card is.” Asked moments later whether he had ever reviewed OpenAI’s Preparedness Framework, he replied, “I don’t know what a preparedness framework is.”
xAI’s safety practices continue to fall short today
xAI’s safety practices have improved over the years, as described in Section I.C. It nonetheless consistently underperforms relative to peers at the frontier: Google DeepMind, OpenAI, and Anthropic.3 Table 1 below shows six core safety practices that each of Google DeepMind, OpenAI, and Anthropic have adopted but xAI has not. (See Appendix I for more information about these companies’ safety practices.) While the safety practices of xAI’s peers vary greatly—and in many cases, fall below the standard to which they should be held—the consistent gap between them and xAI underscores the extent to which xAI is an outlier.
| Practice | xAI | Anthropic | OpenAI | Google DeepMind |
|---|---|---|---|---|
| Publish thorough risk assessments Publishes, for each major frontier model release, a thorough public risk assessment that documents the risk categories considered, the evaluations conducted, and the safeguards applied, in a form that informs external scrutiny. | ✗ | ✓ | ✓ | ✓ |
| Third-party evaluations Consistently engages qualified independent evaluators to conduct risk assessments of its models before deployment. | ✗ | ✓ | ✓ | ✓ |
| Serious misuse incident reporting Publicly reports misuse of the developer’s models by malicious third parties, in a timely manner and with sufficient detail on the activity, the actors, and the developer’s response. | ✗ | ✓ | ✓ | ✓ |
| Safety governance structures Publicly identifies the officers, committees, or councils responsible for AI safety governance. | ✗ | ✓ | ✓ | ✓ |
| Capability elicitation Provides evidence for each major model release that safety testing uses techniques to elicit model capabilities substantially beyond the base level of performance. | ✗ | ✓ | ✓ | ✓ |
| Safeguards against automated AI R&D threats Includes the automation of AI research and development as a threat category with dedicated thresholds and safeguards. | ✗ | ✓ | ✓ | ✓ |
Table 1. Comparison of xAI’s safety practices with those of Anthropic, OpenAI, and Google DeepMind. See Appendix I for more detail, including citations.
Independent assessments confirm xAI’s outlier status. xAI has ranked behind the leading frontier developers in every major published assessment of AI safety practices:
| Assessment | xAI | Anthropic | OpenAI | Google DeepMind |
|---|---|---|---|---|
| SaferAI Risk Management Framework Maturity (October 2025) | 16% | 34% | 33% | 20% |
| FLI AI Safety Index (December 2025) | D | C+ | C+ | C |
| AI Lab Watch Scorecard (September 2025) | 4% | 28% | 18% | 20% |
| Stanford Foundation Model Transparency Index (December 2025) | 14% | 46% | 35% | 41% |
Table 2. Comparison of xAI’s scores in independent assessments of companies’ AI safety practices with those of Google DeepMind, Anthropic, and OpenAI. These assessments also evaluated companies not listed here. In SaferAI’s assessment, xAI ranked eighth out of twelve companies; in FLI’s assessment, it ranked fourth out of eight (with Meta marginally trailing xAI); in AI Lab Watch’s assessment, it ranked fifth out of seven; in Stanford’s Index, it tied for last out of thirteen.
xAI seems to lack sufficient capacity to implement adequate safety practices
Implementing the practices in Table 1 requires dedicated safety personnel and specialized expertise. Anthropic distributes safety work across multiple teams, including Alignment Science, Interpretability, the Frontier Red Team, the Safeguards Research Team, and Societal Impacts, together with oversight structures including the Long-Term Benefit Trust and a Responsible Scaling Officer. OpenAI has approximately 200 staff working across at least five safety-focused teams (Safety Systems, Preparedness, Alignment, Model Policy, and Investigations), alongside a board-level Safety and Security Committee and an internal Safety Advisory Group. Google DeepMind operates multiple safety teams, including AGI Safety & Alignment (30–50 staff as of late 2024), Gemini Safety, and Voices of All in Alignment, plus a Responsibility and Safety Council, an AGI Safety Council, and other oversight bodies.
By contrast, it is unlikely xAI has the capacity to implement the practices in Table 1. According to a 2026 Washington Post article, xAI’s safety team consisted of “just two or three people”; in January 2026, xAI’s senior content-safety team—including the head of product safety, the post-training and reasoning safety lead, and the personality and model-behavior lead—resigned together after a meeting in which Musk had reportedly expressed frustration with restrictions on Grok Imagine. A former employee told The Verge that “safety is a dead org at xAI.” Section III.C addresses what disclosure of forward-looking safety capacity would entail.
B. The Potential Consequences of xAI’s Safety Practices
Grok 3, released in February 2025, benchmarked competitively with leading models from Google DeepMind, OpenAI, and Anthropic. While these companies have also faced safety incidents, xAI’s models have produced an unusual number of them in the 15 months since Grok 3’s release. Grok spontaneously inserted “white genocide” claims into unrelated conversations and questioned the Holocaust death toll (May 2025); endorsed antisemitic conspiracies, praised Hitler, and called itself “MechaHitler” (July 2025); exposed roughly 370,000 user conversations to the open web, including step-by-step instructions for synthesizing fentanyl and methamphetamine, making bombs, and writing malware (August 2025); and generated approximately three million sexualized images of real people over an 11-day period, including roughly 23,000 depicting apparent minors (December 2025–January 2026), with Reuters confirming in controlled testing that even after xAI’s announced fixes, Grok still produced sexualized images in over 80% of initial prompts where other models refused identical requests.
These safety incidents have, in turn, led to an unusual amount of regulatory and litigation exposure. In a roughly seven-week window starting in January 2026, more than a dozen jurisdictions took formal action, multiple national bans on Grok went into effect, 35 state attorneys general issued a joint demand, and federal class actions were filed. See Appendices II and III for more discussion of the regulatory and litigation record.
Drawing clear causal lines between any individual incident and a specific safety practice gap is difficult without the kind of detailed retrospectives that xAI’s peers occasionally publish.4 xAI typically has not provided such retrospectives. Where the company has commented publicly on incidents, it has more often offered post-hoc attributions—most prominently the “rogue employee” explanation—than substantive accounts of what went wrong.
But it is nonetheless possible to draw a link between practice gaps and incidents to varying degrees. For example, Grok’s frequent antisemitic posts in July 2025 immediately followed an announcement by Musk that Grok had been “improved” significantly. xAI later claimed that the incident was due to an unintended change to the model’s system prompt, and a bipartisan letter from sixteen senators concluded that the incident demonstrated “clear and significant gaps in xAI’s pre-deployment development and review process.” Still other connections are more circumstantial. In the weeks before Grok Imagine’s August 4, 2025 launch, a senior xAI safety lead posted publicly that the company “urgently” needed safety-team staffing across the frontier development cycle. xAI proceeded to launch Grok Imagine on schedule with “Spicy” as one of four built-in video generation modes. On her first attempt using the tool, a Verge reporter received a video of Taylor Swift tearing off her clothes, without ever asking for nudity.
C. xAI’s Future is Unclear
Against this backdrop, the company appears to be at a crossroads. It is unclear whether SpaceX will adopt xAI’s frontier AI ambitions. On May 6, 2026, Anthropic and SpaceX announced a partnership giving Anthropic access to a significant portion of its GPU capacity for serving Anthropic’s models; Musk simultaneously announced that xAI would be dissolved as a separate company and folded into SpaceX as “SpaceXAI.” At the same time, Musk has indicated that SpaceXAI is continuing to train future versions of Grok and Cursor recently announced that, together with SpaceXAI, it is training a new model from scratch. Whether SpaceXAI will be a frontier model provider inside a larger holding company, or whether the frontier model business will be wound down in favor of selling xAI’s GPU capacity to xAI’s frontier competitors, is unclear.
If SpaceX does plan to continue xAI’s frontier AI ambitions, will it continue xAI’s approach to safety, or will it invest in the capacity to implement the emerging (though incomplete) industry practices embraced by many of its competitors? xAI’s historical approach to safety, as described above, might provide reasons to be skeptical. But several recent developments offer sources of optimism. In May 2026, xAI signed an expanded agreement with the U.S. Center for AI Standards and Innovation (CAISI) for pre-deployment evaluation of frontier models, including testing in classified environments with safeguards removed, placing it on the same formal footing as Anthropic, OpenAI, Microsoft, and Google DeepMind. On December 30, 2025, xAI updated its safety framework (now called its Frontier Artificial Intelligence Framework) to comply with California’s Transparency in Frontier Artificial Intelligence Act (SB 53). And since May 2025, xAI has published Grok’s production system prompts in a public GitHub repository—a transparency practice that few other frontier developers match. Whether these steps are isolated departures or mark the beginning of xAI’s new attitude toward safety is unclear.
II. Investors’ Right to Know SpaceX’s Frontier AI Plans
Federal securities laws do not impose a fixed list of AI topics that public companies must disclose; instead, they impose principle-based obligations to disclose business risks that a reasonable investor would consider material. Regulation S-K requires disclosure of material information in registered securities offerings and in the periodic reports public companies file with the SEC. 17 C.F.R. § 229. Information is material if “there is a substantial likelihood that a reasonable shareholder would consider it … as having significantly altered the ‘total mix’ of information available.” TSC Industries v. Northway, 426 U.S. 438, 449 (1976). Rule 10b-5 separately prohibits material misstatements and half-truths in connection with the purchase or sale of securities. 17 C.F.R. § 240.10b-5. The substantive content of what must be disclosed therefore evolves with the risk profile of the businesses subject to the rules: new categories of risk can generate new disclosure topics without any change in the underlying legal standard.5
Subsection A identifies the qualitatively new types of risk that frontier AI capabilities are generating. Subsection B identifies an additional risk that would arise if SpaceX moves xAI from its historical fast-follower position toward frontier-leading status. Section III then identifies three categories of disclosure that investors should request of SpaceX in order to understand, and properly price, these risks.
A. The Unique Risk Profile of Frontier AI Companies
The people best positioned to evaluate the risks of frontier AI development have placed those risks in the same tier as pandemics and nuclear war. In May 2023, the CEOs of OpenAI, Anthropic, and Google DeepMind—together with Geoffrey Hinton (now a Nobel laureate in physics), Yoshua Bengio (the Turing Award-winning architect of modern deep learning), and hundreds of additional AI scientists—signed a one-sentence public statement urging that AI-driven extinction risk be treated as a global priority on par with those two threats.6 The International AI Safety Report, chaired by Bengio and authored by more than 100 experts with input from advisors from 29 governments and the U.N., E.U., and OECD, concluded in February 2026 that AI is improving faster than experts had anticipated and that the evidence for risks such as AI-assisted biological weapons development and loss of control of AI systems is growing.
The leading frontier AI companies are actively taking precautions against such risks. The same companies whose CEOs signed the 2023 statement have started designating their models as requiring safeguards that they say would, if removed, expose users to severe harms:
- May 2025: Anthropic activated ASL-3 safeguards for Claude Opus 4, citing the risk that the model could provide meaningful uplift toward CBRN weapons development. Anthropic has maintained safeguards at or above the ASL-3 level since this release.
- August 2025: OpenAI designated GPT-5 as High capability in the Biological and Chemical domains under its updated Preparedness Framework. Subsequent releases—GPT-5.3-Codex, GPT-5.4-Thinking, and GPT-5.5—have each maintained or extended that designation, with GPT-5.4-Thinking (March 2026) the first general-purpose model to operate under High Cybersecurity safeguards.
- May 2025: Google DeepMind reported Gemini 2.5 Pro had crossed the cybersecurity early-warning alert threshold under its Frontier Safety Framework. The threshold has continued to be met by each flagship Gemini release since, and Gemini 2.5 Deep Think (August 2025) additionally reached the early-warning threshold for CBRN uplift.
Each of these designations reflects the company’s own published representation that the model may pose a meaningful risk of severe harm absent the safeguards applied. In other words, leading frontier AI companies are now claiming that their safeguards may be actively necessary to prevent the harms their CEOs and the scientific community have warned about.
The pace of AI development is generating these new risks. Three years ago, the most capable AI systems could autonomously complete software-engineering tasks that might take a human expert roughly five minutes at 50% reliability. By 2026, frontier models are completing tasks that take human experts 12 hours at the same reliability threshold, with task horizons now doubling roughly every three months (compared to every seven months before 2024).7
Each new capability level has, under the companies’ own analyses, expanded the set of harms their safeguards must protect against. If the capability trajectory continues, both the types of risk and their severity will continue to grow.
The categories of harm that the current generation of safeguards is designed to prevent—e.g., uplift to motivated non-state actors in CBRN domains, scaled cyberattacks against major systems—are, in the companies’ own taxonomy, an intermediate risk level. The level above is where risks become potentially catastrophic: a model providing decisive uplift to a state-level biological weapons program, materially increasing the probability that a pandemic-capable pathogen could be engineered, produced, and deployed at scale; or a model capable of substantially automating frontier AI research itself, compounding the rate of capability advance and at which new risk categories emerge. No company has publicly designated a deployed model as having crossed into this tier. But the CEOs of the frontier companies have each indicated their belief that these capabilities will be within reach in the next one to four years.8
Compounding these dynamics, frontier AI development proceeds without the comprehensive federal regulation that constrains other industries with significant risk profiles. In this absence, each company determines its own approach to risk identification and mitigation, which gives investor-facing disclosure a uniquely important role as a window into whether those responsibilities are being discharged.
B. Risks Specific to xAI
The risks identified above apply to every frontier AI company, but SpaceX faces an additional risk layer if it intends to push xAI from fast-follower to frontier-leading status. While Grok has at times briefly led individual benchmarks, no xAI release has opened a new capability paradigm—the kind of step change that defines the leading edge. Google DeepMind’s Gemini 1.5 Pro (February 2024) introduced the first one-million-token context window, several times larger than any predecessor’s; OpenAI’s o1 (September 2024) introduced test-time reasoning as a new scaling dimension, spawning the “reasoning model” category every major company has since adopted; Anthropic’s Claude 3.5 Sonnet with Computer Use (October 2024) was the first frontier model to operate a computer through screen interaction.
Companies that produce such releases bear a distinct safety burden: they encounter new categories of risk first, must characterize them, and in some cases, must develop mitigations from scratch. This work has historically required sizable in-house safety teams of the kind Google DeepMind, OpenAI, and Anthropic maintain (Section I) and xAI does not. Companies behind the leading edge can build on the mitigations and threat models the leading companies have already worked out.
Two implications follow: First, xAI’s safety record to date reflects what can go wrong even when a company is behind the frontier, where risks are smaller and better understood from other companies’ prior work. The same safety practices applied at the uncharted frontier would pose far greater risks. Second, if SpaceX intends for xAI to begin producing paradigm-shifting models, its safety burden rises sharply—moving xAI from the fast-follower side to the first-mover side, encountering new risk categories without prior work to draw on. Whether SpaceX intends to build or acquire commensurate safety capacity, and on what timeline, is a question investors cannot resolve from current disclosures.
III. What SpaceX Should Disclose
For the reasons set out in Section II, SpaceX should disclose at least three categories of information to its prospective public investors: (A) xAI’s track record of safety incidents and any resulting regulatory and litigation exposure; (B) SpaceX’s forward-looking expectations for its AI models’ capabilities and the new risks such capabilities might create; and (C) how the company intends to ensure its products remain safe as those new risks emerge.
A. Track Record: Incidents, Regulation, and Litigation
Investors should understand how xAI’s safety posture has performed under real-world conditions: what has gone wrong, how regulators have responded, what is happening in the courts, and whether these patterns suggest isolated mishaps or systemic problems. The unusually high level of regulatory and litigation exposure includes investigations under E.U. DSA, U.K. OFCOM, Irish DPC, and U.K. ICO authority—proceedings that carry potential fines of 4–10% of global revenue. (See Appendices II and III for further details.) Investors should have the complete inventory of these events, including any not yet in the public record.
Adequate disclosure should allow investors to fully evaluate xAI’s safety record and the company’s response to it, including:
-
Complete safety-incident record. xAI has acknowledged some incidents only after public reporting forced acknowledgment or attributed them to “rogue employees.” Investors should request a complete inventory of safety-relevant incidents—including incidents not in the public record—across all of xAI’s deployed products.
-
Remediation pattern, retrospective and forward. For each material incident, investors should request information answering several critical questions: what was the root cause, what remediation was applied, and has that remediation prevented recurrence of similar failures? Where remediation was confined to surface fixes rather than structural changes, what is the company’s stated plan for structural remediation, and on what timeline relative to its stated capability projections?
-
Proceedings records. Investors should request a complete inventory of active regulatory proceedings, enforcement actions, civil litigation, and orders across all jurisdictions; the company’s potential financial and injunctive exposure in each; and its response posture (remediation, contestation, or non-engagement) in each matter.
B. Forward-Looking Capability and Risk Projections
This category covers where SpaceX is going: its stated capability ambitions and the new risks those ambitions create. The company has sent conflicting signals about whether it will remain a frontier model developer. Its May 2026 announcement folding xAI into “SpaceXAI,” alongside a partnership giving Anthropic access to a significant fraction of its GPU capacity, leaves it unclear whether xAI is still a frontier-AI competitor inside a larger holding company or whether the frontier-model business is being wound down in favor of selling compute to the companies currently at the frontier.
The distinction is material to SpaceX investors. As Section II.B and Section III.A establish, the new capability levels that Google DeepMind, OpenAI, and Anthropic have reached in the past year—and the still-undisclosed capabilities their own projections anticipate—carry qualitatively different risks than the content-safety failures that have characterized xAI’s safety record to date. Investors cannot reasonably price SpaceX’s AI exposure without knowing whether SpaceX intends to develop and deploy models at riskier capability levels or whether it intends only to become a provider of computing infrastructure.
Adequate disclosure should answer the following questions:
-
Frontier ambitions and timeline. Beyond Grok 5, does SpaceX intend to continue training and deploying models at or above the current capability level of frontier models from Google DeepMind, OpenAI, and Anthropic? Does it further intend to produce paradigm-changing releases of the kind discussed in Section II.B—releases that open new capability classes and carry the heightened safety burden described there? If so, by when? If not, are there conditions that would change those decisions?
-
Capability projections. What are the company’s internal capability projections for its frontier-relevant models across capability domains relevant to risk assessment?
-
Projected risks. What categories of risk does the company expect those projected capabilities to create, and what is its assessment of the materiality of each—including risk categories that have been less relevant at xAI’s historical capability level (e.g., CBRN uplift, sophisticated cyber autonomy, AI R&D automation, sophisticated agentic misuse) but that xAI’s own Risk Management Framework identifies as in-scope at higher capability tiers?
C. Safety and Governance Plans
Building on the capability ambitions and risk projections in the previous subsection, this category includes (i) what SpaceX will do to identify and manage the risks those ambitions create, and (ii) the governance structures that determine how those practices are decided, executed, and potentially overridden when they conflict with other commercial interests.9 Section I.A documented xAI’s status as an outlier on the safety practices its peers have converged on and on the organizational capacity required to implement those practices. The questions below track the practices identified in Table 1. The question for each is how SpaceX’s approach will evolve as capabilities and risks scale. Investors should understand:
-
Publish thorough risk assessments. Will SpaceX commit to publishing a thorough risk assessment with each major frontier model release, in form and content adequate for external scrutiny of capability and safeguard claims?
-
Third-party evaluations. Will SpaceX build on the May 2026 CAISI agreement with a regular cohort of qualified external evaluators (e.g., U.K. AISI, METR, Apollo) with access depth and timing adequate to surface what internal evaluation misses?
-
Serious misuse incident reporting. Will SpaceX commit to publishing periodic reports on malicious external use of its models—covering the activity, the actors, and the company’s response—on a defined cadence?
-
Safety governance structures. Will SpaceX designate a named safety officer or committee with deployment authority structurally independent of commercial leadership, and what board-level oversight will apply?
-
Capability elicitation. What will SpaceX do to elicit models’ full capability ceiling—i.e., to approximate what a sophisticated adversary could extract through fine-tuning, agentic scaffolding, or by stripping out safety training?
-
Automated AI R&D threat protection. Does SpaceX recognize automated AI R&D acceleration as its own risk category, with thresholds and safeguards distinct from those applied to other capability domains?
-
Safety capacity. What is xAI’s current safety headcount, and does SpaceX commit to scaling that capacity commensurate with its capability and risk projections and safety and governance plans?
Conclusion
xAI’s safety record is serious enough to warrant scrutiny; but it has not, by itself, foreclosed a better future for the company. The case for the disclosures identified here rests on a more modest premise: that investors deciding whether to put capital into a company that might build frontier AI systems—systems potentially capable of catastrophic-level harms—are entitled to know what that company has done and intends to do to identify and mitigate the risks those systems pose.
The path forward is open. In recent months, xAI has taken modest steps toward the practices on which its peers have converged, suggesting the gap documented in this report is closable. Whether it closes is now a SpaceX decision. The alternative is a SpaceX that develops frontier AI models with the same outlier safety practices that characterized xAI’s first three years.
Investors evaluating the merged entity’s risk profile need to know which of those paths the company has chosen. The disclosure framework set out in this report is neutral on the outcome. It asks only that the choice be made clear to investors and the general public.
Appendices
Appendix I: Comparing xAI’s Safety Practices to Industry Peers
As summarized in Table 1 above, Appendix I identifies six areas where xAI has failed to meet the safety practices of the leading frontier AI companies. The company practice summaries below are based on publicly available information, including the companies’ voluntary safety frameworks, system cards, and other safety reports. Appendix I also summarizes publicly available information about each company’s safety capacity.
1. Publish thorough risk assessments
Publishing risk assessments allows public understanding and scrutiny of how companies manage risks and increases the incentive to do high-quality assessments.
Practice: For each major frontier model release, do companies publish a thorough public risk assessment that documents the risk categories considered, the evaluations conducted, and the safeguards applied, in a form that informs external scrutiny?
xAI: No. xAI maintains no commitment to produce a public risk assessment for each frontier model release, saying only that it “may publish” benchmark results for major releases. In practice, xAI does not regularly publish evaluations of its models: out of more than 16 Grok model releases, it has released system cards that contain evaluations for only 4. Notably, xAI did not release a system card for Grok 3, a major release, and has not released a system card for Grok 4.3, its most capable model to date.
Anthropic: Yes. Anthropic publishes detailed system cards for each model release detailing risk categories considered, evaluations conducted, and safeguards applied. Anthropic’s Responsible Scaling Policy v3.2 also commits to publishing comprehensive Risk Reports “every 3–6 months.” Risk Reports cover Anthropic’s activities as a whole rather than a single model, documenting threat models, capability and alignment evaluations, risk mitigations across security and deployment safeguards, and overall risk analyses. Anthropic also commits to publishing updates to its risk analysis whenever it deploys a new model significantly more capable than those covered in the most recent risk report.
OpenAI: Yes. OpenAI’s Preparedness Framework commits to publishing Preparedness findings for major deployments, including the scope of testing performed, capability evaluations corresponding to tracked threat models, and (for models beyond a “High” risk threshold) information about the safeguards implemented to mitigate risks. It also commits to producing internal Capabilities and Safeguards Reports to inform its Safety Advisory Group. As a matter of practice, OpenAI publishes system cards for each major model release describing risk evaluations, what risk thresholds models have reached, and what safeguards were implemented.
Google DeepMind: Yes. Google DeepMind’s Frontier Safety Framework version 3.1 says that the company will conduct a “critical capability assessment” prior to the first external deployment of a new frontier model. For subsequent versions of the model, the company says it will conduct a new assessment if the model has meaningful new capabilities that could pose new levels of risk. The company does not commit to publicly releasing these assessments; however, it did in fact release the assessment for Gemini 3 Pro, its first major model release following the publication of FSF version 3, when the risk assessment policy was announced. The assessment covered risk categories, evaluations conducted, and safeguards applied. Previously, the company had published similar information in system cards.
2. Third-party evaluations
Independent evaluators provide a credible external check on a model developer’s internal practices and can help improve the quality and effectiveness of their work through specialized expertise.
Practice: Do companies have a record of consistently engaging with qualified independent evaluators to conduct risk assessments of its models before deployment?
xAI: No.
- xAI has so far announced only a handful of engagements with independent evaluators. xAI has only publicly indicated a single case of engaging an independent evaluator in model testing: In the original version of Grok 4’s system card, xAI reported that the U.K. AI Security Institute conducted chemical/biological uplift and cyber evaluations of Grok 4. xAI removed these claims shortly thereafter without explanation. There is no public record of whether xAI worked with the U.K. AISI for its several model deployments since. This contrasts with Anthropic, OpenAI, and Google DeepMind, who have all regularly engaged with independent pre-deployment evaluators for multiple years.
- xAI also collaborated with SecureBio to develop an internal benchmark of benign and restricted biology and chemistry queries used to measure Grok’s dual-use capabilities; however, there is no indication that SecureBio itself evaluated Grok.
- xAI signed a pre-deployment evaluation agreement to test future models with the U.S. Center for AI Standards and Innovation (CAISI) this May, although it is unclear when this will take effect.
Anthropic: Yes.
- Anthropic’s Responsible Scaling Policy commits to seeking public external review of Risk Reports in certain high-risk scenarios, with appointed third-party reviewers receiving unredacted or minimally redacted access to publish comprehensive commentary on Anthropic’s reasoning, evidence, and risk decisions. The policy authorizes Anthropic’s Long-Term Benefit Trust to request external reviews and approve the selection of reviewers.
- Anthropic signed a voluntary MOU with CAISI in August 2024, among the first AI companies to do so, and has had an ongoing pre-deployment testing relationship with the U.K. AI Security Institute. The first-ever joint U.S./U.K. AISI pre-deployment evaluation by both institutes was of Anthropic’s upgraded Claude 3.5 Sonnet in October 2024.
- Anthropic collaborated with CAISI and U.K. AISI on stress-testing its Constitutional Classifiers—a defense system used to prevent jailbreaks—for models including Claude Opus 4 and 4.1, with government red-teamers identifying vulnerabilities both before and after deployment.
- U.K. AISI conducted alignment evaluations of Claude Opus 4.1, Sonnet 4.5, and a pre-release snapshot of Opus 4.5 as part of an ongoing collaboration, with access to the models’ full chain-of-thought reasoning.
- METR conducted external reviews of Anthropic’s Risk Reports, including a March 2026 review of the Sabotage Risk Report for Claude Opus 4.6, with access to unredacted documents.
- Apollo Research has evaluated multiple Claude models for scheming and deception, with findings published in Anthropic’s system cards—including a notable evaluation of Claude Opus 4 in May 2025 that identified concerning behaviors like attempts to write self-propagating worms and leave hidden notes for future model instances.
- In July 2024, Anthropic launched a funding initiative for third-party organizations to develop evaluations measuring capabilities relevant to the AI Safety Levels in its Responsible Scaling Policy.
- Anthropic and OpenAI ran a joint pilot alignment evaluation exercise in mid-2025, in which each lab ran its internal alignment evaluations on the other’s publicly released models.
OpenAI: Yes.
- OpenAI’s Preparedness Framework discusses, at a high level, involving external third parties in the risk evaluation and mitigation process described in the framework.
- OpenAI was among the first companies to sign a voluntary MOU with CAISI in August 2024, and has had a pre-deployment testing relationship with the U.K. AI Security Institute since 2024. CAISI and U.K. AISI jointly conducted pre-deployment testing of o1, and both institutes separately tested GPT-5.5 with access to checkpoints that had reduced refusals.
- OpenAI gave CAISI early access to ChatGPT Agent, leading to the discovery of two novel security vulnerabilities.
- Other external evaluators OpenAI partners with include METR (autonomous capabilities, since GPT-4), Apollo Research (scheming and deception), and SecureBio (biological capabilities via the Virology Capabilities Test).
- OpenAI’s November 2025 post on external testing describes three forms of third-party collaboration: independent evaluations, methodology reviews, and subject-matter expert probing. The post notes that some evaluators receive direct chain-of-thought access and access to models with safety mitigations removed.
- OpenAI and Anthropic ran a joint pilot alignment evaluation exercise in mid-2025, in which each lab ran its internal alignment evaluations on the other’s publicly released models.
Google DeepMind: Yes.
- Google DeepMind’s Frontier Safety Framework discusses, at a high level, involving external third parties in the risk evaluation and mitigation process described in the framework.
- Google DeepMind has partnered with the U.K. AI Security Institute since its inception in November 2023, and the institute has conducted pre-deployment testing of models including Gemini 1.0 Ultra and Gemini 3. In March 2026, Google DeepMind expanded the relationship into a broader research partnership covering chain-of-thought monitoring, joint publications, and societal impact research.
- Google DeepMind partners with external evaluators on independent assessments, including Apollo Research, Vaultis, and Dreadnode, most recently for Gemini 3.
- Google DeepMind published a 2024 paper, Holistic Safety and Responsibility Evaluations of Advanced AI Models, outlining its approach to external evaluation, including structured third-party model access infrastructure designed to reduce risks of providing model access to evaluators.
3. Serious misuse incident reporting
Frontier AI developers are uniquely positioned to observe how their models are being misused. Public misuse reports create a shared resource that the private and public sectors can use to strengthen defenses.
Practice: Do companies publicly report misuse of their models by malicious third parties, in a timely manner and with sufficient detail on the activity, the actors, and the developer’s response?
xAI: No. xAI maintains no formal commitment to public incident disclosure. They have published no threat-intelligence reports or disclosures of malicious external use of Grok. They also have no documented coordination with other labs on shared threats.
Anthropic: Yes. Anthropic maintains a Transparency Hub where, among other safety-related topics, they list multiple misuse reports they have produced and released publicly, including:
- A March 2025 misuse report covering social media manipulation campaigns and misuse by novice actors.
- An August 2025 misuse report covering a large-scale data extortion campaign, North Korean employment fraud at U.S. tech companies, and AI-generated ransomware.
- A state-sponsored cyber-operations disclosure (November 2025) covering a Chinese group’s use of Claude Code in coordinated attacks against dozens of organizations.
OpenAI: Yes. OpenAI has published several public reports on misuse of its models, including:
- A joint disclosure with Microsoft (February 2024) about their disruption of five state-affiliated cyber operations from four countries.
- A report on covert influence operations (May 2024) detailing five disrupted influence campaigns across four countries.
- A standalone disclosure of a covert Iranian influence operation (August 2024) that included U.S. election content.
- An omnibus update (October 2024) presenting case studies from detected cyber and covert influence operations.
- An update (February 2025) covering surveillance tooling and state-linked influence activity across a few countries.
- A mid-2025 update covering state-linked malware development and IT worker fraud.
- A late-2025 update covering surveillance activity and large-scale scam operations apparently linked to the P.R.C.
Per its G7 HAIP transparency report, OpenAI treats public disclosure as discretionary.
Google DeepMind: Yes. Threat-intelligence disclosure is run primarily by the Google Threat Intelligence Group (GTIG), which sits within Google Cloud / Mandiant rather than DeepMind. GTIG (in some cases jointly with DeepMind) has published:
- A report on adversarial misuse of Gemini (January 2025) analyzing how state-backed actors from several countries used the model through 2024.
- A late-2025 AI Threat Tracker (November 2025) documenting the first observed AI-integrated malware used in live operations.
- An early-2026 AI Threat Tracker (February 2026) covering further AI-integrated malware, growing actor interest in agentic tooling, and large-scale model-extraction campaigns.
- A mid-2026 AI Threat Tracker (May 2026) covering AI-assisted zero-day exploitation industrial-scale AI-augmented cyber operations.
4. Safety governance structures
Organizations are more likely to successfully implement and adhere to their safety policies when named decision-makers are accountable for governance.
Practice: Do companies publicly identify the officers, committees, or councils responsible for AI safety governance?
xAI: No. xAI’s Frontier Artificial Intelligence Framework designates unspecified “risk owners” responsible for risk mitigation. The framework names no officer, committee, or board mechanism responsible for AI safety governance.
Anthropic: Yes. Section 4 of Anthropic’s Responsible Scaling Policy (RSP) establishes the Responsible Scaling Officer (RSO), who approves deployment decisions and oversees policy implementation. Changes to the RSP require Board approval in consultation with the Long-Term Benefit Trust (LTBT), an independent body designed to help Anthropic achieve its public benefit mission. The RSP specifies that the RSO and LTBT have formal authorities over Risk Reports, which are “determinations about whether to continue AI development and deployment in light of the risks.” The CEO and RSO jointly approve each Risk Report, then notify the Board and LTBT. The LTBT can request external review of Risk Reports, approves Anthropic’s selection of external reviewers, and receives regular briefings from Anthropic. When marginal risk analysis—the argument that Anthropic’s marginal contribution to industry-wide risk is small enough to justify proceeding, even when absolute risk may be high—plays a major role, the Board and LTBT must also formally approve.
OpenAI: Yes. The Safety and Security Committee (SSC) oversees and reviews OpenAI’s safety and security processes and practices for model development and deployment. The SSC can require mitigation measures up to and including halting the release of any model or AI system, even where applicable risk thresholds would otherwise permit release. On safety and security issues, the PBC Board must consider only the Mission, not the pecuniary interests of stockholders or any other interest.
Additionally, the Preparedness Framework specifies that a Safety Advisory Group (SAG) is appointed by the CEO and reviews proposed deployments and recommends next steps to the CEO. SAG recommendations are non-binding and the CEO makes the final deployment decision.
Google DeepMind: Yes. Google DeepMind names two standing internal bodies on its website: the Responsibility and Safety Council, co-chaired by COO Lila Ibrahim and VP of Responsibility Helen King, and the AGI Safety Council, led by Co-Founder and Chief AGI Scientist Shane Legg. The current Frontier Safety Framework v3.1 (April 17, 2026) does not specify what exact role these bodies play.
5. Capability elicitation
Model evaluations should elicit a model’s capabilities to approximate what a sophisticated adversary could achieve.
Practice: Do companies provide evidence for each major model release of eliciting capabilities substantially beyond baseline performance during safety testing?
xAI: No. In practice, xAI does not regularly publish evaluations of its models: out of at least 16 Grok model releases, it has released system cards that contain evaluations for only four. Notably, xAI did not release a system card for Grok 3, a major release, and has not released a system card for Grok 4.3, its most capable model to date. The Grok 4 system card does mention that xAI removed safeguards and gave the model tools during evaluation, and the Grok 4.1 system card also briefly mentions removing safeguards. But no system cards have been released since then, despite xAI releasing multiple models with superior capabilities and therefore a higher risk profile.
Anthropic: Yes. The Claude Opus 4.7 system card states that they “use standard best-practice elicitation methods—including helpful-only training (i.e. a model with behavioral harmlessness safeguards trained away).” In its chemical and biological risk evaluation methodology section , Anthropic also notes that it iteratively refines prompting by analyzing failure cases, equips models with tools and agentic harnesses, and uses extended thinking in most evaluations.
OpenAI: Yes. OpenAI’s Preparedness Framework specifies that evaluations are intended to approximate the full model capabilities that an adversary could extract, including by using the highest-capability tier of system settings, a separate model variant with negligible safety refusals, and best-available scaffolds. The framework notes that given the “continuous progress in model scaffolding and elicitation techniques,” this capability elicitation is regarded as a “lower bound, rather than a ceiling.”
Google DeepMind: Yes. Google’s Frontier Safety Framework says that model capabilities are augmented in evaluations to reflect realistic threat scenarios, including via scaffolding and added inference compute. Their latest Frontier Safety Framework Report states that “evaluations of Gemini 3 Pro benefit from increased attempt budgets, longer step limits, and enhanced tool affordances compared to prior generations.” For its cybersecurity testing, Google DeepMind equips it with command-line and web search tools, and guides it through a structured reasoning process. For its AI research evaluations, it uses an external scaffold developed by METR.
6. Safeguards against automated AI R&D threats
Models that meaningfully accelerate AI R&D may create a feedback loop, causing capabilities to rapidly outpace the safety and oversight mechanisms designed to govern them.
Practice: Do companies include the automation of AI research and development as a threat category with dedicated thresholds and safeguards?
xAI: No. xAI does not treat AI R&D acceleration as a threat category in their Frontier Artificial Intelligence Framework. It is mentioned briefly, under Operational and Societal Risks (p. 8), as a transparency metric: xAI may “assess the percent of code or percent of pull requests at xAI generated by our models.” No thresholds or safeguards are specified for this risk.
Anthropic: Yes. Anthropic treats AI R&D as a dedicated capability threshold in their Responsible Scaling Policy. The policy defines an “Automated R&D in key domains” threshold which triggers if either (1) models can fully substitute for Anthropic’s Research Scientists and Engineers at competitive cost (within a factor of 5), or (2) the rate of AI progress doubles and the doubling is plausibly attributable to AI R&D automation (pp. 8–9). Anthropic’s plans at this threshold include ambitious security research aimed at defending against the world’s best-resourced attackers, comprehensive logging and monitoring of internal AI development, systematic alignment assessments, an improved ability to internally red-team their deployment safeguards, and externally reviewed Risk Reports.10
OpenAI: Yes. “AI Self-improvement capabilities” is one of three Tracked Categories in OpenAI’s Preparedness Framework. Their High threshold is defined as equivalent to giving every researcher “a highly performant mid-career research engineer assistant,” and a Critical threshold is defined that would merit a halt in further development until adequate safeguards are identified.
Google DeepMind: Yes. Google treats AI R&D as a dedicated risk domain in its Frontier Safety Framework. The framework’s first risk threshold, “ML R&D acceleration level 1,” is reached when a model has been used to accelerate AI development to a rate substantially above historical rates (p. 15). At this threshold, Google recommends higher security standards, and a supplemental safety case justifying that residual risk has been reduced to an acceptable level (p. 7). The framework also names a general suite of deployment safeguards it may draw on, but does not bind them to specific thresholds (pp. 6, 13).
Safety capacity
In addition to the six specific practices highlighted above and compared in Table 1, there is also a notable difference in the safety capacity of xAI relative to the leading frontier developers.
Companies require dedicated personnel, expertise, and structures to implement industry best practices such as those described here. Without the organizational capacity to actualize the practices described above, even well-written commitments cannot be reliably implemented or enforced. The following summarizes publicly available information about the safety capacity at each company.
xAI: As of 2026, there is no dedicated safety team at xAI, with one former employee telling The Verge that “Safety is a dead org at xAI.” According to The Washington Post, in 2025 the safety team consisted of “just two or three people.”
Anthropic: Safety capacity is distributed across multiple named teams:
- Alignment Science (technical research on misalignment risks)
- Interpretability (mechanistic interpretability)
- Frontier Red Team (cybersecurity, biosecurity, autonomous systems evaluations)
- Safeguards (deployment infrastructure, safety mechanisms, user policies)
- Safeguards Research Team (introduced 2025, jailbreak robustness, monitoring): current named members include the team lead plus nine others, with the team actively hiring
- Societal Impacts (technical research on real-world impact)
Committees:
- Long-Term Benefit Trust
- Plus the Responsible Scaling Officer role and quarterly Board noncompliance reporting
OpenAI: Safety is distributed across multiple teams. As of May 2026, approximately 200 people work across these teams. These teams include:
- Safety Systems (guardrails and evaluations)
- Preparedness (focused on OpenAI’s Preparedness Framework)
- Alignment (ensures models are aligned with human values)
- Model Policy (develops the model spec)
- Investigations
There are also oversight committees at OpenAI focused on AI safety, including:
- Safety and Security Committee (board-level)
- Safety Advisory Group (internal staff committee)
Google DeepMind: As of late 2024, Google DeepMind had the following safety teams:
- AGI Safety & Alignment (mechanistic interpretability, scalable oversight, dangerous capability evaluations, and work on the Frontier Safety Framework). In August 2024, 30–50 people were working on Google’s AGI Safety & Alignment team.
- Gemini Safety (focusing on safety training for the current Gemini models)
- Voices of All in Alignment (focused on alignment techniques for value and viewpoint pluralism)
Committees:
- Responsibility and Safety Council (evaluates Google DeepMind’s research against Google’s AI Principles)
- AGI Safety Council (safeguard Google DeepMind’s processes, systems, and research against extreme risks that could arise from powerful AGI systems in the future)
- Launch Review Forum (approves model releases and application launches)
In addition, there are other teams at Google whose work overlaps with their AI capacities:
- Trust & Safety (addressing product abuse and content)
- Responsible Innovation team (implements Google’s AI Principles)
- Novel AI Testing Team
- Content Adversarial Red Team
There is also the AGI Futures Council at Google that provides perspectives and recommendations to the Board and management team on long-term opportunities, risks, and impacts associated with the development of AGI.
Appendix II: Government Responses to Grok Incidents
| Date | Type of Action | Regulatory Body | Action | Status |
|---|---|---|---|---|
| 8/5/2024 | Warning letter | Five U.S. Secretaries of State | Secretaries of state from five states (MN, PA, WA, MI, and NM) sent an open letter to Elon Musk urging him to implement changes to Grok after it shared with millions of users false information suggesting that Kamala Harris was not eligible to appear on the 2024 presidential ballot. | |
| 2/27/2025 | Formal investigation | Office of the Privacy Commissioner (Canada) | Canada’s Office of the Privacy Commissioner (OPC) opened a formal investigation into X over the use of Canadian users’ data for AI training. | Ongoing. |
| 4/11/2025 | Formal investigation | Data Protection Commission (Ireland) | Ireland’s Data Protection Commission opened an inquiry into whether X violated the GDPR by using E.U. users’ X posts to train Grok. The DPC previously sought an injunction against X for this practice from the Irish High Court, in response to which X agreed to suspend its use of E.U. users’ data for model training. | Ongoing. |
| 7/11/2025 | Formal criminal investigation | Paris Prosecutor’s Office (France) | The Paris Prosecutor’s office opened an investigation into X, looking into concerns about fraudulent data extraction and politically-motivated manipulation of the algorithm. | Ongoing. The investigation has since been expanded to include concerns about the generation of nonconsensual deepfakes and CSAM, as well as Holocaust denialism. In February 2026, police from French authorities raided X’s offices in Paris. As part of the broader investigation, Elon Musk and former X CEO Linda Yaccarino were summoned to appear before prosecutors in April 2026. Both individuals appear to have ignored these requests by law enforcement. DOJ has declined to cooperate with the French investigation. |
| 7/11/2025 | Warning letter | Members of U.S. House and Senate | Members of the House and Senate sent multiple letters to xAI following Grok’s antisemitic and pro-Hitler outputs. These include bipartisan House and Senate letters to Elon Musk asking for transparency about xAI’s safety practices and why the incidents occurred. Ten Jewish Members of Congress and Sen. Elizabeth Warren also authored letters to Secretary of Defense Hegseth expressing concern about the Pentagon’s use of Grok in light of the incidents. Sen. Warren’s letter also expressed concern about xAI’s access to sensitive government data. | |
| 8/5/2025 | Enforcement | U.S. General Services Administration | Wired reported that the GSA removed xAI’s Grok from the Multiple Award Schedule (long-term government-wide contracting program) following MechaHitler and similar incidents. In August 2025, the GSA announced in a press release that it would add ChatGPT, Claude, and Gemini to MAS through contractor Carahsoft. | As of May 2026, according to the GSA’s website, Grok is now available via MAS through Carahsoft. |
| 12/18/2025 | Warning letter | Garante (Italy) | The Garante (Italian data protection authority) issued a warning to users of Grok and other AI tools over the use of these tools for NCII. The Garante noted it was coordinating with the Irish Data Protection Commission, which is conducting its own investigation into X. | The Garante later issued a press release requesting from the Italian parliament powers to block access to platforms that enable deepfakes. |
| 1/2/2026 | Enforcement | MeitY (India) | Indian authorities ordered X to make immediate changes to Grok to restrict the generation of sexually explicit material. The country’s IT ministry warned that noncompliance could jeopardize X’s immunity from liability for user-generated content. | X blocked over 3,500 pieces of content and deleted more than 600 accounts in response to the warning. News media reported that government officials remained dissatisfied, but no subsequent government action has been reported. |
| 1/8/2026 | Formal investigation | eSafety Commissioner (Australia) | eSafety (Australia online safety regulator) sent a request for further information to X about the safeguards in place to prevent the misuse of Grok on X. The regulator cited reports of the use of Grok to generate sexualized and exploitative imagery. eSafety later confirmed it opened an investigation into xAI in response to complaints Grok was used to create CSAM. | Ongoing. |
| 1/10/2026 | Enforcement | Komdigi (Indonesia) | The Indonesian government temporarily blocked access to Grok on X, citing concerns over NCII. | The block was lifted after X committed to addressing the issues and complying with applicable laws. Indonesian authorities said they would consider implementing the block again if future violations occurred. |
| 1/11/2026 | Enforcement | MCMC (Malaysia) | Malaysia blocked access to Grok in response to concerns about NCII. Authorities cited that X’s responses to regulatory notices focused primarily on user reporting mechanisms for inappropriate content and failed to address the underlying issues with the model. | The country restored access to Grok after X implemented additional safety measures. |
| 1/12/2026 | Formal investigation | Ofcom (U.K.) | Ofcom (independent U.K. communications regulator) opened a formal investigation into X over reports of AI-generated NCII and CSAM. The agency flagged potential violations of the U.K. Online Safety Act. | Ongoing. |
| 1/14/2026 | Formal investigation | California Attorney General | The California Attorney General launched an investigation into xAI over reports of generation of NCII and CSAM and demanded immediate action to prevent the generation of this content. This was followed by a cease and desist letter demanding the company take immediate action to stop the creation and distribution of CSAM. This cited multiple potential violations of multiple California civil and criminal laws, including Civil Code § 1708.86, which authorizes civil penalties of $25,000 per violation ($50,000 with malice) for facilitating the creation of NCII or CSAM. | Ongoing. In its cease and desist letter, the AG’s office stated that it “appreciate[s] your company’s recent announcement that it is implementing new guardrails regarding xAI’s creation and distribution of sexualized content.” |
| 1/14/2026 | Preliminary review | PIPC and KMCC (South Korea) | South Korea’s Personal Information Protection Commission (PIPC) launched a preliminary fact-finding review into Grok in response to NCII concerns. Korea’s Media and Communications Commission (KMCC) also demanded stronger youth protections from X, setting a two-week deadline to address concerns before fines would be levied. | Neither the PIPC nor the KMCC has publicly announced a formal investigation, fine, or enforcement order against xAI/X arising from the deepfake controversy. |
| 1/15/2026 | Formal investigation | Office of the Privacy Commissioner (Canada) | Canada’s Privacy Commissioner expanded its existing investigation of X Corp. and launched an investigation into xAI in response to reports Grok was being used to generate NCII. | Ongoing. |
| 1/16/2026 | Administrative request | Cabinet Office (Japan) | Japan’s Cabinet Office asked X to curb the output of NCII generated by Grok. It also submitted a written inquiry regarding what measures X has taken to prevent the generation of these images. | |
| 1/16/2026 | Enforcement | DICT / NTC / CICC (Philippines) | The Philippines blocked access to Grok amid concerns about NCII and CSAM. | The block was lifted on January 21 in response to corrective actions. |
| 1/20/2026 | Warning letter and subsequent order | Senacon / ANPD / Federal Prosecutors (Brazil) | Three Brazilian public agencies issued a joint recommendation demanding that X take measures to prevent the generation of NCII, and imposing a 30-day deadline to remove existing NCII generated by Grok on the platform. On February 11, the Federal Prosecutor’s Office demanded that X submit within five days proof of measures taken to prevent Grok from generating NCII, as well as monthly reports with details about the company’s actions to address the issue and remove harmful posts. Authorities said that X was not transparent about the previous measures it claimed to have taken in response to the issue, failing to provide information on the specific incidents of concern. | Public information does not disclose subsequent measures taken by Brazilian authorities. |
| 1/23/2026 | Warning letter | 35 U.S. State Attorneys General | A bipartisan group of 35 state attorneys general issued a demand that xAI take additional action to prevent Grok from generating NCII and CSAM. The AGs demanded that xAI share how it intends to ensure that Grok is no longer capable of producing this content and eliminate content that had already been produced. | |
| 1/26/2026 | Formal investigation | European Commission (E.U.) | The European Commission launched a new formal investigation against X under the E.U. Digital Services Act (DSA). The investigation will assess “whether the company properly assessed and mitigated risks” associated with the deployment of Grok into X, including the generation of NCII and CSAM. The investigation will also cover whether X met its responsibility to conduct a risk assessment report for the EC for the use of Grok’s functionalities on X. The EC has the power to impose fines for DSA violations of up to 6% of a company’s global annual revenue. The Commission also extended its December 2023 proceedings against X about whether X properly assessed and mitigated all systemic risks associated with its recommender systems to encompass the impact of its switch to a Grok-based recommender system. | Ongoing. |
| 2/3/2026 | Formal investigation | Information Commissioner’s Office (U.K.) | The U.K.’s data protection regulator—the Information Commissioner’s Office (ICO)—announced an investigation into xAI and X in the aftermath of media reporting regarding the use of Grok to create sexualized images and videos of real people. The maximum fine available is 4% of annual revenue. | Ongoing. Shortly after the announcement, new criminal laws establishing offenses for creating non-consensual intimate AI-generated images of adults came into effect. |
| 2/17/2026 | Referral for criminal prosecution | Council of Ministers / Public Prosecutor’s Office (Spain) | The Spanish cabinet requested that the Fiscal General (attorney general) initiate a criminal investigation into X, Meta, and TikTok for their alleged role in producing and spreading AI-generated CSAM. | The Fiscal General has yet to initiate criminal proceedings. Once the Fiscal General receives a referral from the cabinet, the office must undergo a consultation process before initiating proceedings. |
| 2/17/2026 | Formal investigation | Data Protection Commission (Ireland) | Ireland’s Data Protection Commission (DPC) opened an investigation into X for possible violations of the GDPR related to the creation and dissemination of NCII. The commission will investigate whether X unlawfully processed personal data of E.U. subjects, including children, in generating these images. The maximum fine available is 4% of annual revenue. | Ongoing. |
| 2/19/2026 | Warning letter | U.S. House Energy & Commerce Committee Democrats | U.S. House Energy and Commerce Committee Democrats sent a letter to Elon Musk demanding information about xAI’s role in promoting NCII and CSAM. The letter demanded information about X’s policies about explicit image generation, what safeguards were in place, and how many images had been removed. |
Appendix III: Selected Grok-Related Lawsuits
| Date | Case | Court | Summary | Status |
|---|---|---|---|---|
| 9/23/2025 | Campact eV v. X.AI LLC | Hamburg Regional Court (Germany) | Liability suit brought against xAI by the Campact association, a German nonprofit advocacy group. Campact alleged that Grok had falsely claimed on X that Campact was financed “to a large extent by federal funds.” | The Hamburg Regional Court granted Campact’s request for a preliminary injunction against xAI, saying that the company would be subject to a fine of up to €250,000 per future repetition of the false claim. |
| 1/15/2026 | St. Clair v. XAI Holdings Corp. | Southern District of New York (U.S. federal) | Suit by Ashley St. Clair (mother of one of Elon Musk’s children) against xAI after Grok was used to create sexualized deepfakes of her. St. Clair alleges that this continued even after she notified xAI of the behavior. St. Clair alleges violations of state tort law as well as New York’s anti-revenge porn law. | Ongoing. St. Clair filed an amended complaint on February 3, 2026. The court is deciding whether to transfer the case to the Northern District of Texas. |
| 1/23/2026 | Doe v. X.AI Corp. (Berger Montague Class Action) | Northern District of California (U.S. federal) | Class action lawsuit alleging that Grok “humiliates and sexually exploits women and girls” through the generation of nonconsensual explicit deepfakes. The amended complaint’s proposed class is all U.S. individuals who “had real images of themselves altered and disseminated by xAI/Grok to produce sexualized or revealing images or videos with their faces and/or other distinguishing features reasonably identifiable without their consent,” with sub-classes for minors, and Ohio, New Jersey, and South Carolina plaintiffs. Plaintiffs bring state-law claims based on tort and consumer protection. | Ongoing. Plaintiffs filed an amended complaint on May 1, 2026. The parties are briefing whether the plaintiffs may proceed anonymously. |
| 2/19/2026 | Offlimits and Fonds Slachtofferhulp v. X / xAI | Amsterdam District Court (Netherlands) | Sexual and online abuse advocacy organizations sued xAI demanding that it cease offering the functionality to generate NCII and CSAM through Grok. xAI argued that it had implemented technical safeguards preventing Grok from being able to generate NCII and CSAM as of January 20, 2026. A hearing occurred on March 12, 2026. | On March 26, 2026, the Amsterdam District Court ordered the company to immediately stop its models from generating NCII and CSAM, imposing a penalty of €100,000 per day for noncompliance, capped at €10,000,000 per defendant. The court found that the generation of non-consensual undressing images violates the GDPR and Article 6:162 of the Dutch Civil Code, rejecting xAI’s argument that liability lay with the user who issued the prompts to generate the images. |
| 3/16/2026 | Doe 1 v. X.AI Corp. (Lieff Cabraser Class Action) | Northern District of California (U.S. federal) | Class action lawsuit alleging Grok used plaintiffs’ photographs to produce CSAM. Complaint alleges that xAI “failed to test the safety of the features it developed and implemented for use on Grok to prevent AI-generated CSAM” and “received multiple direct reports that Grok was being used to digitally alter photographs of real minors into sexually explicit images, yet failed to take adequate remedial action.” The proposed class is all U.S. individuals “who had real images of themselves as minors altered by xAI/Grok to produce sexualized images or videos with their faces and/or other distinguishing features reasonably identifiable.” The suit alleges violations of Masha’s Law (federal child sexual violence law) and the Trafficking Victims Protection Act, as well as California tort and consumer protection law. Masha’s Law imposes statutory damages of $150,000 per violation. | Ongoing. The court related the case to the Berger Montague class action, so both cases are now proceeding before Judge Casey Pitts. |
| 3/24/2026 | Mayor and City Council of Baltimore v. X Corp. et al. | Circuit Court for Baltimore City (Maryland state court) | Municipal suit alleging that xAI violated Baltimore’s consumer protection laws and engaged in deceptive and unfair trade practices by marketing Grok as generally safe for users, despite its ability to generate NCII and CSAM. It argues that xAI’s own purported rules against non-consensual sexual content are “deceptive misrepresentations.” The suit seeks statutory penalties and injunctive relief. | Ongoing. |
Footnotes
-
A MASK score under 50% means that when pressured to lie, the model contradicted its own stated beliefs less than half the time. ↩
-
xAI noted that because the model “is intended for agentic coding applications and we do not expect it to be widely used as general-purpose assistant [sic], the current MASK evaluation results do not currently pose serious concerns.” ↩
-
This report compares xAI’s safety practices to those of Google DeepMind, OpenAI, and Anthropic. By most measures, these three companies have led frontier AI development over the past few years. They have also consistently been early adopters of safety practices. For example, they were the first three companies to publish safety frameworks and the only companies to do so before the 2024 Seoul Summit, at which 16 companies committed to publish frameworks of their own. ↩
-
See, for example, Anthropic’s report on the use of their models by Chinese state-sponsored actors for cyber-espionage and OpenAI’s reports on model sycophancy and accidentally grading model chain-of-thought during training. xAI did publish an informal analysis of the MechaHitler incident on the Grok X account, but has not publicly addressed the causes of other incidents in detailed reports. ↩
-
The SEC’s evolving treatment of cybersecurity is the closest recent analog to the risks emerging from frontier AI. The Division of Corporation Finance’s 2011 CF Disclosure Guidance: Topic No. 2 did not announce a new rule for cyber risks and incidents, instead clarifying that such risks could be material under existing Regulation S-K line items (Items 105, 303, 101, 103) and existing antifraud principles. The Commission’s 2018 Commission Statement and Guidance on Public Company Cybersecurity Disclosures ratified and extended that view, tying cyber disclosure to Sarbanes-Oxley § 302 disclosure controls and to the Rule 10b-5 prohibition on half-truths. Only in 2023 did the Commission adopt codified rules requiring specific disclosures for cyber risks (Regulation S-K Item 106; Form 8-K Item 1.05 for material incidents). Each step added enforcement mechanisms, but the underlying obligation rested throughout on the same materiality standard applied to a new category of risk. ↩
-
The full statement reads: “Mitigating the risk of extinction from AI should be a global priority alongside other societal-scale risks such as pandemics and nuclear war.” Signatories include Sam Altman (OpenAI), Demis Hassabis (Google DeepMind), Dario Amodei (Anthropic), Geoffrey Hinton, Yoshua Bengio, and hundreds of additional AI scientists and public figures. ↩
-
In March 2025, METR (Model Evaluation and Threat Research) established the 50% task-completion time horizon metric and reported a historical doubling time of approximately seven months, assessing models released 2019 to 2024. In late January 2026, METR updated its doubling-time estimate to approximately 89 days, using an expanded task suite. And as of today, METR estimates the 50% task-completion time horizon of Claude Opus 4.6 at approximately 12 hours. ↩
-
In March 2025, Anthropic submitted recommendations to the U.S. Office of Science and Technology Policy regarding how to “better prepare America to capture the economic benefits and national security implications of powerful AI systems.” Anthropic noted that it “expect[ed] powerful AI systems will emerge in late 2026 or early 2027”; by “powerful AI systems” it meant AI systems with “[i]ntellectual capabilities matching or exceeding that of Nobel Prize winners across most disciplines,” the “ability to navigate all interfaces available to a human doing digital work today,” the “ability to autonomously reason through complex tasks over extended periods,” and the “ability to interface with the physical world.” In a 2024 podcast interview with Lex Fridman, Anthropic CEO Dario Amodei discussed his anticipated timeline for when AI systems will become capable enough to warrant a higher security level: “I would be very, very surprised if it was 2030. I think it’s much sooner than that.”
Such speculation is not limited to Anthropic. Sam Altman, CEO of OpenAI, predicted this past February that we would see a “superintelligence tipping point” by 2028, when “more of the world’s intellectual capacity could reside inside of data centers than outside of them.” And Demis Hassabis, CEO of Google DeepMind, remarked at a 2025 summit on AI that “AGI [artificial general intelligence], probably the most transformative moment in human history, is on the horizon.” ↩
-
xAI’s published Risk Management Framework is itself a forward-looking representation about how the company identifies and mitigates risk from frontier AI development. Under Rule 10b-5’s half-truth doctrine, SpaceX must not render that representation misleading, meaning material gaps between xAI’s published commitments and SpaceX’s actual practices have legal significance for SpaceX’s disclosure obligations. Cf. In re Massey Energy Co. Sec. Litig., 883 F. Supp. 2d 597 (S.D. W. Va. 2012). ↩
-
Note that in Anthropic’s Frontier Compliance Framework—its legally binding safety commitments under California’s Transparency in Frontier AI Act—it identifies automated AI R&D as a risk category but does not commit to these specific mitigations. ↩