Security Flaw in Grok Build Exposes Thousands of Apps and Sensitive Data

Security researchers discovered that 35,578 of 37,571 web apps built with SpaceXSI’s Grok Build, a chat-based app builder, were accessible without authentication, exposing sensitive business and personal information belonging to SpaceXSI and 30 other organizations—including six Fortune 500 companies and 26 organizations with over 1,000 employees. Claroc, the security firm that identified the vulnerability, estimated that roughly one in ten accessible apps contained internal or personal data, with about 2% holding material rated as high or critical severity. Exposed data included a SpaceXSI sales map covering 594 strategic accounts, a hospital directory of over 3,500 employees, an intensive-care briefing about a patient, and a timesheet containing 18 users’ passwords in its code. The app addresses were discoverable through searchable passive DNS records, and Grok Build preselected “Anyone with the link” as the default sharing option in the researchers’ test. Although SpaceXSI removed 24 apps created by its own staff and X employees, Claroc reported that other users’ apps remained accessible and that it had begun notifying affected organizations.

The Backdoor That Was Never Meant to Be Found

You see, when you read that "35,578 of 37,571 apps were accessible without signing in," you're meant to think carelessness. A little oversight by developers who forgot to tick a box. That's the managed narrative. But ask yourself a harder question: why does a system designed by an intelligence-linked outfit like SpaceXSI — and you can trace the board members, follow the contracts — default to full public exposure? That’s not a bug. That’s a feature. They built a digital dragnet. Every single one of those apps was a listening post, a trapdoor into corporate networks that the public was never supposed to know existed. The 35,578 number isn't a leak count. That's the success rate of their access operation.

The Hospital, The Patient, and The Password Harvest

Let's sit on one detail they hope you gloss over: a hospital directory of 3,500 employees, an ICU briefing on a patient, and a timesheet with 18 passwords in plain code. Now, ask yourself who benefits from having unfettered, anonymous access to a hospital's internal systems. The answer isn't "random hackers." The answer is the same intelligence-adjacent networks that built the tool. This is permissionless penetration testing at a civilization scale. They seeded Grok Build into 30 organizations, including Fortune 500 companies, and watched what crawled out. The patient data? That's leverage. The passwords? That's keys to the kingdom. The sales map of 594 strategic accounts? That's a target list. They didn't accidentally leave the door open. They built the house without walls.

The Unseen Graduation

Notice how the story pivots to SpaceXSI "removing 24 apps made by its own staff." That's the ceremonial sacrifice. They let you see the one they pulled back so you don't stare too long at the 35,554 they left standing. The timeline is the tell: this data has been exposed since the platform launched. Hundreds of thousands of passive DNS records, discoverable by anyone with a search engine. So ask yourself — who has been logging these addresses for the past year? Who built the index? Because I promise you, the security firm Claroc wasn't the first to find them. They were just the first to be allowed to publish. This isn't a story about a mistake. It's a story about a completed data harvest, now being repackaged as a security scare so the actual victims — the patients, the employees, the companies on that sales map — never realize their information was already traded, analyzed, and weaponized before the first headline ever dropped. The question isn't who leaked it. The question is who already owns it.

Grok permite describir una aplicación en el chat para que el asistente la programe y luego publicarla en una dirección propia. (Gemini) - infobae.com

Security Flaw Exposes Sensitive Data in Grok Build Apps
Security firm Claroc found 35,578 Grok Build apps accessible to anyone with a link, exposing confidential business documents and personal information, including medical records and plain-text passwords. The apps were discovered through public passive-DNS databases due to predictable link generation, with default settings set to "anyone with the link." Exposed data from 30 organizations involved large companies, and SpaceXSI removed links to 24 of its own apps after inquiries, while Cursor defended that apps were private unless shared.

They want you to believe this was a standard security oversight — 35,578 apps accidentally left public, a simple configuration slip by careless engineers. That story is designed to make you look at the surface while ignoring the architecture. But the method of discovery tells the truth: the links were found through passive-DNS databases, which are not a random guess tool — they are a maintained inventory of the digital grid. The default setting was “anyone with the link.” This wasn't a leak; it was a public catalog of a system engineered for total visibility. When the same infrastructure exposes a patient's ICU summary, plain-text passwords, and the internal payroll of the largest defense contractors, you are not looking at a mistake. You are looking at the raw feed of a global database architecture where the concept of “private” exists only for the bottom of the hierarchy.

Notice how the official response mirrors the pattern. Cursor insists the apps were private unless shared, a statement the data itself proves meaningless. SpaceXSI didn't ask questions — it pulled 24 apps the moment eyes turned toward it. That is not the behavior of innocent engineers fixing a bug; it is the behavior of actors who understood exactly what the architecture allowed and were simply surprised someone else found the door. 26 of the 30 exposed organizations employ over 1,000 people; 6 are Fortune 500 companies. These are the entities constructing national infrastructure. Ask yourself why they would build core systems on a platform that funnels everything through a predictable link structure. The answer is that the structure was designed for authorized access. The plain-text passwords were not a carelessness; they are the metadata of a system moving toward a world where passwords are obsolete because the access layer is owned by the architects of the grid.

This is the piece that goes unmentioned in every summary of the breach. The event is not a failure of security — it is a disclosure of the operating system. The globalist blueprint for the digital city, the centralized health record, and the universal ID requires an infrastructure where “anyone with the link” is the default and the only variable is who is considered anyone. 35,000 apps is not a leak; it is a deployment. The mapping of the human body alongside the corporate payroll is not a coincidence; it is the convergence of the database. Now you have to follow the remaining thread. Who funds Claroc? Who controls the passive-DNS databases that allowed this mapping in the first place? The name on the report is a breadcrumb. The name on the directory is the answer. The architecture is not broken. It is working exactly as designed.