AI Coding Tools Under Fire: Grok Build Uploads Entire Git Histories, Claude Code Suspected of Silent Transfers
Security researcher cereblab exposed how Grok Build and Claude Code engage in unauthorized data collection that goes far beyond user expectations, turning routine code assistance into large-scale repository exfiltration.
In a controlled test with a 12 GB local Git repository, Grok Build 0.2.93 created two independent HTTPS channels. The primary channel handled task context at roughly 192 KB, while a background storage channel silently repacked and uploaded the entire .git directory in 75 MB chunks, consuming 5.10 GiB of traffic to a Google Cloud Storage bucket named grok-code-session-traces. This produced a 27800-fold difference between expected and actual outbound volume.
The upload logic activated regardless of explicit user instructions such as "do not read" placed on marker files, proving that the behavior is a hardcoded data-collection routine rather than an artifact of the model's understanding. Privacy controls proved ineffective: the client-side improve_model_enabled flag is completely decoupled from the server-side trace_upload_enabled flag, allowing uploads to continue even after users disable model-improvement features.
Although xAI later disabled the uploads via remote configuration on 13 July, the full repository-upload code remained present in the 0.2.99 binary, merely gated by a server flag. The exposed Git history includes deleted .env files, credentials, connection strings, and commit records that reveal vulnerability-fix timelines, enabling attackers to infer unpatched issues in similar codebases.
Parallel findings emerged for Claude Code, whose client maintains multiple WebSocket connections that periodically transmit file paths, dependency trees, and code fragments even without an active coding task. No local logs, switches, or data-flow documentation are provided, and the closed-source binary prevents independent verification of additional hidden routines.
A side-by-side traffic audit of major tools produced clear results:
- Grok Build: full .git directory, Git history packaged, privacy switch ineffective, confirmed silent upload.
- Claude Code: suspected file-level and metadata exfiltration, details undisclosed, silent-transfer behavior confirmed.
- Codex: only current context fragments, no Git packaging, privacy controls effective, no anomalous reports.
- Gemini: no active uploads detected.
Analysts attribute the pattern to fundamental conflicts between commercial model-training demands and user data sovereignty, excessive server-side control over local clients, and the absence of mandatory third-party audits for closed-source AI binaries.
Recommended defenses include physical network blocking of known endpoints, running tools inside Docker containers that mount only read-only directories without .git, pre-processing repositories with git filter-repo, deploying eBPF monitoring with alerts for sessions exceeding 10 MB, and favoring auditable open-source options such as Continue.dev or locally hosted Ollama models.
Related articles
Agent-Ops 0.4.0 Released: Methodology for Secure Human-AI Collaboration in IT Operations
Sergey Zhitinsky, founder of Git in Sky, has published the public normative candidate for Agent-Ops 0.4.0, an open industry methodology governing how engineers and AI agents jointly handle IT infrastructure tasks. The framework keeps humans firmly in the decision-making loop while using deterministic programs for data collection and approved changes. It addresses risks such as prompt injection through processed data, unverified model outputs, and unclear accountability when AI recommendations lead to incidents. The methodology divides work across eight explicit steps and three separate planes: data, governance, and independent verification performed by a Guardian role. Two additional companies have joined as maintainers following agreements at the IT Elements 2026 conference, turning the project into a multi-organization effort. Contributors are invited to help refine contracts, schemas, and operational scenarios through GitHub and GitVerse.
ProxyKey MCP: Securing API Access for AI Agents Without Exposing Credentials
ProxyKey has released an MCP server that allows AI coding agents such as Claude Code and Cursor to manage API credentials without ever reading the actual secret values. The solution addresses the risk that any key visible to an agent becomes compromised through logging, tracing, or prompt injection. Real provider keys are stored encrypted with AES-256-GCM and never returned by any API endpoint after initial entry. Agents instead receive limited virtual passes that support IP binding, rate limits, TTL, and detailed request logging. A pending-secret workflow lets agents prepare services before the real token exists, with the human entering the secret only through a web panel. The approach deliberately restricts the MCP tool contract so no operation can read or return secret values.
Shadow AI in CI/CD: Why AI Agents Must Be Modeled as Security Threats
A new analysis from the CNCF highlights the growing risks of Shadow AI within continuous integration and continuous deployment pipelines. The report argues that AI agents should be treated as potential threats rather than simple productivity tools. Starting from a developer's laptop and extending to Kubernetes clusters, these agents can introduce unauthorized access paths and data exposure risks. Security teams are urged to incorporate AI agent behavior into formal threat modeling exercises. The discussion emphasizes the need for visibility and control over autonomous AI components operating in production environments.
Detecting Lateral Movement with Neural Networks Trained Solely on Synthetic Data
A researcher generated entire corporate network histories using a 135-line configuration file to create synthetic authentication logs containing lateral movement attacks. Neural networks trained exclusively on these artificial datasets were then evaluated against 1.65 billion real authentication events from Los Alamos National Laboratory, including 749 red team events across 301 compromised machines. The best ensemble of six models flagged 3.6 million hourly machine windows and placed 16 genuine attacks among the top 23 highest-scoring entries, producing only seven false positives. In comparison, a simple threshold counter required 161,000 false alarms to reach the same detection level. The approach also demonstrated an iterative feedback loop where detector errors directly informed refinements to the synthetic world generator. The work shows that synthetic data can reach AUC performance comparable to models trained on real labeled attacks while providing full control over the underlying attack definitions.