Grok Build AI Coding Assistant Secretly Uploaded Entire User Repositories Including Git History and Secrets to Google Cloud
Grok Build, the command-line AI coding assistant created by xAI, was discovered sending complete user repositories — including full Git history and long-deleted secrets — to Google Cloud storage, often without any legitimate need to access the files.
Security researcher Cereblab identified the issue after analyzing network traffic between the Grok Build CLI and xAI servers. The tool was observed packaging entire repositories into Git archives and uploading them wholesale, even when the user explicitly instructed it to answer “OK” and forbade any file access.
Scope of the Data Exposure
Unlike competing tools such as Claude Code, Gemini, and Codex, which typically open only the specific files required for a task, Grok Build transmitted significantly larger volumes of data. In multiple tests, the assistant uploaded full project histories containing passwords, access keys, and other credentials that developers had removed from the current working tree months earlier but remained in Git history.
One user reported that Grok Build also exfiltrated the entire home directory, exposing SSH keys, password-manager databases, and additional sensitive material.
Company Response and Technical Fix
Following the public report, xAI engineers activated the server-side parameter disable_codebase_upload and set it to true for all users, immediately halting the mass uploads. The company also claimed to operate in a zero-data-retention (ZDR) mode for accounts with the setting enabled and offered the /privacy command to disable retention and delete previously synced data.
Cereblab disputed the effectiveness of these measures, stating that the /privacy command only affected session-level storage and did not stop the underlying repository uploads. The researcher emphasized that secure defaults should prohibit transmission of codebases rather than require users to opt out manually.
Further Actions and Remaining Concerns
Elon Musk publicly stated that xAI would completely delete all user data collected before the fix. On July 12, the company open-sourced Grok Build, removed usage restrictions, disabled data storage by default, and began deleting previously stored code while allowing local execution of the tool.
Although these steps address future behavior, independent verification that all previously uploaded repositories, commit histories, and secrets have been erased remains impossible. The episode highlights fundamental risks in AI coding assistants that process source code in the cloud without transparent, user-controlled data-handling policies.
Related articles
Microsoft Copilot Abused to Accelerate Corporate Account Takeovers and Bank Transfer Frauds
Cybercriminals can leverage Microsoft Copilot to speed up the compromise of corporate accounts and execute financial frauds. In a controlled simulation, researchers demonstrated how the AI assistant helped redirect a $247,500 bank transfer after gaining access to an employee's email. The attack begins with the creation of inbox rules that automatically delete suspicious login alerts, followed by rapid analysis of internal communications to identify high-value targets. Copilot was then used to replicate the victim's writing style and craft a convincing phishing email capable of stealing session tokens and bypassing multi-factor authentication. Once the executive account was taken over, the tool quickly located pending payments and generated a fraudulent request to alter the recipient bank details. The scenario highlights risks from legitimate AI features rather than any specific vulnerability in Copilot itself.
Vibe Hacking Rises: Generative AI Lowers Barriers for Offensive Security Operations
Generative AI is reshaping the cybersecurity threat landscape by dramatically reducing the cost of offensive security knowledge. Previously, attackers needed years of experience in reverse engineering and exploit development to conduct meaningful intrusions, but AI now assists with research, code generation, debugging, and adapting known techniques to new environments. This enables less experienced individuals to build functional attack chains in weeks rather than years. The article introduces the concept of vibe hacking, where attackers collaborate with AI assistants using natural language prompts in a process similar to vibe coding. Defenders can no longer rely on the scarcity of skilled adversaries and must shift toward continuous validation frameworks such as CTEM, AEV, and PTaaS. Senior human experts remain essential for risk judgment and business context, even as automation accelerates routine tasks.
Hunt.io Exposes Suspected Chinese Cyber Espionage Operation Using Agentic LLMs Claude Code and DeepSeek
In July 2026 Hunt.io published research on a suspected Chinese cyber espionage campaign uncovered through an exposed directory on a Hong Kong server. The leak contained 2,431 files including victim source code, operation logs, web shells, exploitation scripts, scan results and phishing page clones. Researchers identified traces of Claude Code and DeepSeek-v4-pro working together, with Claude Code handling agentic tasks and session context while DeepSeek supported reasoning, script refinement and next-step selection. The infrastructure cluster, known as TencShell, showed overlapping SHA-256 HTTP headers, SSH host keys and TLS certificates across 13 IP addresses. Multiple initial access vectors were observed, including SQL injection against Taiwanese and Thai government targets plus exposure of Supabase and Azure secrets. The report also references a parallel Anthropic disclosure on GTG-1002, another Chinese state-linked operation that used Claude Code for 80-90 percent of tactical work.
OWASP LLM10 Unbounded Consumption: Testing YandexGPT Lite 5 and GigaChat Lite on Resource-Intensive Prompts
The article examines OWASP LLM10: Unbounded Consumption, a category focused on attacks that force large language models to perform computationally expensive tasks without traditional denial-of-service traffic. Researchers used the AI Red Team platform to evaluate two flagship Russian models, YandexGPT Lite 5 and GigaChat Lite, against prompts designed to trigger recursive context expansion, fractal nesting, combinatorial explosions, and multi-agent simulations. The study highlights how a single carefully crafted prompt can generate disproportionate token consumption, GPU load, and API costs compared with conventional DoS methods. Both models demonstrated defensive strategies including hard generation limits at 512 tokens, graceful degradation by summarizing instead of expanding, and early refusal with alternative suggestions. The work was supported by the Foundation for Assistance to Innovations and aims to improve architectural protections for LLM applications. Examples of tested prompts and observed model behaviors are provided for research and educational purposes only.