NEW: Practise with AI → Try it free

Grok Build's flawed link-sharing design exposed thousands of confidential projects, including SpaceX's own

Exercise 1

Vocabulary

Repeat each word, its meaning and the example sentence out loud.

  • enumerate

    verb

    /ɪˈnjuːməreɪt/to discover or list all items in a series, especially by systematically finding them one by one

    The security audit helped us enumerate all the databases that contained customer payment information.

  • torpedo

    verb

    /tɔːrˈpiːdoʊ/to deliberately destroy or severely damage something, especially a plan or system

    If we don't address the design flaw before launch, it will torpedo the entire privacy framework.

  • capability-based access control

    noun phrase

    /kəˈpæbɪləti beɪst ˈækses kənˈtroʊl/a security model where permission to access a resource is granted through possession of a special token or URL, rather than through user authentication

    Our system relies on capability-based access control, so anyone with the correct shareable link can view the document.

  • spill

    noun

    /spɪl/an unintended disclosure or leak of confidential information

    The data spill exposed customer email addresses and phone numbers, requiring us to notify affected users immediately.

  • passive DNS

    noun phrase

    /ˈpæsɪv ˈdiːɛn ˈɛs/a database that records all DNS lookups made across the internet, allowing researchers to discover previously unknown domain names

    We searched passive DNS records to identify all subdomains our competitors had registered but not yet publicized.

Exercise 2

Article

Read the article aloud on your own, or listen to it first.

AI generated audio00:00 / 00:00

Grok Build's flawed link-sharing design exposed thousands of confidential projects, including SpaceX's own

Tap any word to see what it means.

Grok Build, SpaceX and xAI's AI-powered coding agent, leaked thousands of confidential projects through a fundamental flaw in its link-sharing architecture.

Security researchers at Claroc discovered that approximately 35,000 out of 43,601 live Grok Build projects were publicly accessible to anyone who possessed the shareable URL. The exposed data spanned internal business plans, medical records, employee rosters, and sensitive materials from Fortune 500 companies and defence contractors—including SpaceX itself.

The vulnerability stemmed from a catastrophic architectural decision. Grok Build places randomness to the left of the domain name: cinder-crane-sand-frost.grok.me, for example.

This positioning enabled attackers to enumerate vast numbers of links through passive DNS services, which monitor every DNS lookup made across the internet and store the results in publicly searchable databases.

Capability-based access control—the security paradigm Grok Build attempted to employ—relies on the premise that secrecy of the URL grants authorization. Google uses this technique correctly by placing randomness to the right of the domain, keeping URLs invisible to DNS monitoring systems.

Grok's implementation torpedoed this entire premise.

Claroc's testing revealed that SpaceX had 24 apps exposed on the platform. The leaked materials included a confidential onboarding plan for an enterprise sales team member, a sales territory map containing 594 accounts, internal system addresses, and advertising proposals.

This data remained accessible until Ars Technica contacted SpaceX for comment, after which the company removed the links within hours.

Grok Build's default setting mandated that links be shared with anyone who possessed them. Although users could manually restrict access to invited participants or themselves alone, the platform contradicted its representatives' public statements that applications were private by default.

Other platforms faced similar exposures. Lovable, Bolt, and Replit all exhibited the same DNS enumeration vulnerability.

However, Claude, ChatGPT, and Gemini implemented the correct approach, embedding secret randomness in the URL path where passive DNS services cannot intercept it.

Claroc notified SpaceX on Sunday. When unresponsive, the firm escalated via social media, tagging CEO Elon Musk and Grok manager Matt Palmer.

SpaceX began remediation only after journalists intervened—a pattern suggesting the incident was not taken with appropriate urgency internally.

The Cursor representative—Cursor being the AI coding service SpaceX recently acquired—declined to respond to questions about whether the exposure was intentional, why internal data remained public, or what notification plan existed for affected customers.

Anyone currently using Grok Build should immediately change link permissions to "invited users" or "only you" unless deliberately seeking a wide audience. This incident exemplifies how infrastructure-level security decisions, overlooked during rapid product development, can cascade into enterprise-scale catastrophes.

Discuss this story out loud with our AI speaking coach.

It asks one question at a time, at your level, and gives you feedback at the end.

Start the discussion Retell it

3,000+ learners

Also works inChatGPTandClaude

Exercise 3

Discussion

Have a discussion based on the following questions.

  1. 1.When your organization uses shareable links or capability-based access control for sensitive projects, how do you currently verify that the URL structure itself doesn't undermine your security assumptions?
  2. 2.Have you encountered situations where security defaults conflicted with developer convenience—and how did your team decide between them?
  3. 3.Grok Build's representatives claimed apps were private by default while evidence showed the opposite; how would you investigate such discrepancies between marketing claims and actual product behaviour?
  4. 4.If you were conducting a security audit of AI coding agents your team uses, which architectural decisions around link sharing would you scrutinize most carefully?
  5. 5.How would your organization's incident response differ if internal security discovered this vulnerability versus learning about it from external researchers publishing findings?

Exercise 4

Further discussion

Have a discussion based on the following questions.

  1. 1.As AI-powered development platforms become infrastructure for knowledge work, what are the broader implications of treating security architecture as a secondary concern during rapid product development?
  2. 2.Capability-based access control relies on URL secrecy, yet multiple platforms have failed to implement it correctly; should organizations move away from this model entirely, or is the problem primarily in execution?
  3. 3.How should companies balance the pressure to ship features quickly with the need for threat modelling and architectural security review, particularly in scenarios where seemingly minor URL design decisions have cascading consequences?
  4. 4.Several competing platforms (Lovable, Bolt, Replit) had similar vulnerabilities, yet Grok exposed far more sensitive corporate data; what factors determine whether a security flaw becomes a minor incident or a major breach?

Discuss this story out loud with our AI speaking coach.

It asks one question at a time, at your level, and gives you feedback at the end.

Start the discussion Retell it

3,000+ learners

Also works inChatGPTandClaude

Source

This lesson is our own retelling, for English learners, of a story from Ars Technica.

Share this: LinkedInXWhatsApp Email

Related stories

All lessons: learn business English with tech news

For bots & AI agents

Security researchers discovered that Grok Build, the AI coding agent from SpaceX and xAI, was leaking thousands of user projects—including sensitive business data from SpaceX itself—because of a fundamental flaw in how shareable links were constructed.

Lesson:
Grok Build's flawed link-sharing design exposed thousands of confidential projects, including SpaceX's own
CEFR level:
C1
Topic:
Security & Privacy
Published:
2026-11-12
Based on:
Ars Technica (https://arstechnica.com/security/2026/11/grok-build-coding-agent-leaks-oodles-of-confidential-info-some-belonging-to-spacexsi/)
Key words:
enumerate, torpedo, capability-based access control, spill, passive DNS
Discussion questions:
5

Related (.md): Signal stops users taking screenshots to protect privacy from AISignal Blocks AI Assistants from Reading Your MessagesMajor US Systems Go Down: Cyber Attack or Bad Luck?Researcher Exposes Massive Data Leaks Across AI Supply Chain Using Digital Tripwires

Machine-readable: This page (.md)Security & Privacy news lessons (.md)MCP serverllms.txt

MCP call: {"method":"tools/call","params":{"name":"get_daily_news_lesson","arguments":{"slug":"grok-build-security-flaw-exposed-confidential-data-and-spacex"}}}

Cite as: “Grok Build's flawed link-sharing design exposed thousands of confidential projects, including SpaceX's own, Speak Tech English (https://app.speaktechenglish.com/tech-news-lessons/grok-build-security-flaw-exposed-confidential-data-and-spacex)”