Oleksandr Kuzmenko, EditorPublished 7 min readAI-assisted · editor-reviewed
TL;DR
- Subdomain-based sharing exposes secret project URLs to passive DNS indexing tools.
- Over 35,000 Grok Build applications leaked internal databases, rosters, and roadmaps.
- Path-based sharing (used by Claude, ChatGPT, and Gemini) prevents DNS logging leaks.
Key facts
- Exposed grok.me subdomains found
- 43,601
- Publicly accessible apps without auth
- ~35,000 (nearly 95%)
- Entropy of 3-word slug
- ~38 bits
- SpaceXSI internal apps found leaking
- 24
Source: Key facts — Exposed grok.me subdomains found, SpaceXSI internal apps found leaking
Source: Key facts. Exposed grok.me subdomains found: 43,601. SpaceXSI internal apps found leaking: 24. The chart compares only values that share a unit. Each figure is copied from the story.
Metric chart
- 43,601Exposed grok.me subdomains found
- 24SpaceXSI internal apps found leaking
- Exposed grok.me subdomains found43,601
- SpaceXSI internal apps found leaking24
The Flaw in Subdomain-Based Sharing
Vibe-coding agents let developers generate functional web applications from prompts within minutes. To enable fast sharing, platforms like Grok Build create links formatted as https://cinder-crane-sand-frost.grok.me. While the three-word slug yields approximately 38 bits of entropy, placing randomized capability identifiers into the subdomain completely undermines the model.
Passive DNS monitoring services capture newly queried Fully Qualified Domain Names whenever a browser or testing environment resolves them. Because subdomains are exposed in DNS queries, Claroc researchers could query public DNS databases and locate 43,601 live grok.me records without needing to brute-force URLs.
Scope of Exposed Enterprise Data
Of the discovered addresses, approximately 35,000 links (nearly 95%) allowed unauthenticated access to the underlying apps and databases. Claroc verified exposures across major organizations:
- 24 internal SpaceXSI applications, including a 594-account enterprise sales territory map and sales onboarding plans.
- A Peruvian construction firm dashboard displaying 3,784 employee medical exam results.
- Tesla service center scorecards listing 22 technicians with performance bonuses.
- Rosters and technical proposals belonging to US Navy contractors, hospitals, and aerospace groups.
Platform Comparisons and Mitigation
Platforms such as Lovable, Bolt, and Replit follow the same vulnerable subdomain deployment model. By contrast, Claude Artifacts (claude.ai/public/artifacts/), ChatGPT (chatgpt.com/share/), and Gemini (gemini.google.com/share/) protect secret keys inside the URL path, preventing DNS infrastructure from exposing them. SpaceXSI removed the 24 internal apps after contact, but default link sharing often leaves projects open to anyone with the link unless explicitly changed to invited users only.
When to use
- Use vibe-coding deployment links only for disposable mockups containing synthetic test data.
- Opt for platforms embedding authorization tokens in URL paths when sharing unauthenticated prototypes.
When NOT to use
- Never use default public preview links for vibe-coded applications handling proprietary APIs, internal databases, or PII.
- Avoid platforms that rely solely on randomized subdomains for capability-based authorization without authentication.
What to do today
- Audit live deployments across Grok Build, Lovable, Bolt, and Replit for hardcoded credentials or customer data.
- Switch app privacy settings from public link access to invited users only.
- Require company SSO or authenticated sessions for any internal operational tools built with vibe-coding agents.
Step names are taken from What to do today.
Step names are taken from What to do today. Audit live deployments across Grok Build, Lovable, Bolt, and Replit for hardcoded credentials or customer data.. Switch app privacy settings from public link access to invited users only.. Require company SSO or authenticated sessions for any internal operational tools built with vibe-coding agents.
- Audit live deployments across Grok Build, Lovable, Bolt, and Replit for hardcoded credentials or customer data.
- Switch app privacy settings from public link access to invited users only.
- Require company SSO or authenticated sessions for any internal operational tools built with vibe-coding agents.