Codex

8 articles tagged with this keyword.

Latest

Developer Spends $9,000 on AI Agents to Build Crossweft Tool for Enforcing Multi-Language Component Agreements
Findy to Host AI×Security Conference 2026 on Rapid AI Evolution and Core Defense Principles
AI Agents Codex and Grok Generate Passing Tests That Fail to Verify Cookie Signatures and Security Logic
OpenAI Deactivates Three-Year-Old Pro Account Used for Bug Bounty Work, Permanently Cutting Off All Chat History and Files
Zhou Hongyi Warns AI Tools Are Industrializing Vulnerability Discovery
Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest
OpenAI ChatGPT Computer History Feature on macOS Could Expose Detailed User Activity Logs to Infostealers
AI Coding Tools Under Fire: Grok Build Uploads Entire Git Histories, Claude Code Suspected of Silent Transfers
AI Security

AI 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.

安全客Jul 28, 2026Translated from Chinese

Grok Build AI Coding Assistant Secretly Uploaded Entire User Repositories Including Git History and Secrets to Google Cloud