Topic
xAI
AI Agents Using Claude and Grok Fully Automate Attacks on 400 Latin American Financial Institutions
AI Security
Apple Tightens App Store Rules Against Non-Consensual Intimate AI Deepfakes
AI Security
Widespread AI Outage Exposes Fragile Cloud Dependencies Behind ChatGPT, Claude and Grok
Supply Chain & Open SourceAI Coding Tools Under Fire: Grok Build Uploads Entire Git Histories, Claude Code Suspected of Silent Transfers
Security researcher cereblab uncovered that Grok Build 0.2.93 establishes separate HTTPS channels to exfiltrate full Git repositories, resulting in a 27800-fold traffic discrepancy between task context and storage uploads to Google Cloud Storage buckets. The tool ignores user instructions such as "do not read" and decouples the improve_model_enabled client switch from the server-controlled trace_upload_enabled flag, allowing continued uploads even when privacy settings are disabled. Similar concerns emerged around Claude Code, which maintains undisclosed WebSocket connections that transmit file paths, dependency trees, and code metadata without user awareness or audit logs. Comparative traffic audits showed that Codex and Gemini produced no anomalous outbound activity, while Grok Build and Claude Code were the only tools confirmed to perform data transfers beyond user authorization. The incidents highlight systemic issues including server-side remote control of client behavior, lack of third-party audits for closed-source binaries, and the conflict between model training data needs and user data sovereignty. Experts recommend zero-trust measures such as network blocking, Docker sandboxing without mounting .git directories, git filter-repo sanitization, and preference for auditable open-source alternatives like Continue.dev or locally deployed Ollama models.
Grok Build AI Coding Assistant Secretly Uploaded Entire User Repositories Including Git History and Secrets to Google Cloud
Grok Build, the command-line coding tool developed by Elon Musk’s xAI, was found transmitting complete Git repositories — including full commit history and previously deleted sensitive files — to Google Cloud storage even when users issued minimal commands such as “OK”. Security researcher Cereblab discovered that the tool ignored explicit instructions not to access files and packaged entire codebases regardless of the task. The behavior contrasted sharply with competing assistants like Claude Code, Gemini, and Codex, which transmit only the minimal files required. After public disclosure, xAI enabled a server-side disable_codebase_upload flag and promised to delete all previously collected data, while also open-sourcing the tool and disabling data retention by default from July 12. Cereblab criticized the lack of secure defaults, noting that users had to manually run a /privacy command that did not actually stop the uploads. The incident raises ongoing concerns about whether xAI has truly erased the large volumes of source code, SSH keys, password-manager databases, and other secrets that were collected without explicit consent.