A recent analysis by cybersecurity expert Aprozper revealed alarming vulnerabilities in Grok Build, a platform for developing applications. A passive DNS search uncovered 43,601 links associated with the domain grok.me, with more than 35,000 of these links—approximately 95 percent—identified as public. This means that simply clicking these links grants access to the corresponding applications and the sensitive data they contain. Aprozper’s investigation indicated that Grok’s default privacy setting automatically permits access to anyone with the link. Users, while able to adjust this setting to “invited users” or “only you,” may not realize they are sharing private information by default.
In a contrasting statement from a spokesperson for Cursor, the AI coding service recently acquired by SpaceXSI, it was asserted that Grok Build applications are set to private by default, allowing for public access only at the creator’s discretion. However, Aprozper’s findings challenge this claim, demonstrating that Grok Build often requires users to actively change access settings to restrict visibility.
The issues uncovered extend beyond Grok; Aprozper noted that other app-building platforms such as Lovable, Bolt, and Replit also expose sensitive data via shared links. Despite these platforms permitting the creation of individual web addresses for apps—which can similarly reveal sensitive information—Grok Build stood out for exposing the highest volume of sensitive company data.
This incident raises critical concerns about the safety of data shared through links across various AI coding platforms. Notably, options provided by Claude’s published artifacts, ChatGPT’s shared conversations, and Gemini adhere to stricter privacy protocols, ensuring the anonymity of the links shared by employing unique, randomized paths that are not indexed in the DNS, thereby enhancing confidentiality.
The Cursor representative did not respond to subsequent inquiries regarding whether SpaceXSI intentionally exposed proprietary information, the decision to delete sensitive data following an inquiry, or whether there would be communication to users about their own data vulnerabilities. Consequently, it is advisable for Grok Build users to opt for the “invite others” setting when sharing applications unless they fully intend for their creations to be publicly accessible.
The situation underscores an important reality for business owners concerning the risks of data exposure and vulnerabilities in app-sharing practices. Understanding potential adversarial tactics as defined in the MITRE ATT&CK framework is crucial; tactics such as initial access and data exposure could likely have played a role in this situation. Organizations must remain vigilant, regularly reviewing settings and sharing practices to mitigate risks associated with unintended data exposure.