Source time Edition date
Grok Build coding agent leaks oodles of confidential info, some belonging to SpaceXSI
Grok Build's exposure of 35,000 open apps puts xAI and SpaceX data at risk, a warning for anyone deploying coding agents near sensitive codebases.
Judgment
SpaceXSI must decide whether to change Grok Build's default link sharing and move random tokens behind the domain, trading fast internal sharing for protection against DNS enumeration; security chiefs at affected firms must decide whether to block link-based apps until notifications arrive.
Basis
Claroc said a passive DNS search returned 43,601 links ending in grok.me, and Aprozper said more than 35,000 opened the app and its stored data. Aprozper said tests showed Grok Build defaults to “Anyone with the link,” while a Cursor representative said apps are private by default and nothing goes public unless shared. The mechanism is the URL design: Grok puts random dice words left of grok.me, so passive DNS can enumerate them; Google puts randomness right of the domain. Claroc found 24 SpaceXSI apps exposing material, including a sales territory map of 594 accounts, and said links for all 24 later returned “app not found.”
- Links ending grok.me43,601
- Public linksmore than 35,000
- SpaceXSI apps24
- Sales territory accounts594
Unclear The source does not say whether SpaceXSI will change the default setting, rotate exposed URLs, or notify every affected organization beyond the 24 internal apps.
Next Check whether Grok Build's default link setting changes to “invited users” or “only you,” and whether the 24 SpaceXSI links continue to return “app not found.”