SlowMist flags Grok CLI upload mechanism for possible .env and RSA key exposure

The cybersecurity firm expanded its review to include permission and execution risks, warning Grok Build CLI could expose sensitive files and allow unrestricted tool use under certain settings.

Summary

SlowMist said its review of Grok Build CLI found multiple security weaknesses spanning data upload, permission handling and command execution. The firm said the repository upload mechanism could send git bundles containing sensitive files such as .env files and RSA private keys, while the command "cargo check" was classified as safe in a way that could enable remote code execution when paired with malicious instructions. SlowMist also said the bypassPermissions setting in .claude/settings.json could circumvent permission checks and allow unrestricted tool execution, and that the permission model inherited from Claude Code CLI carries similar risks. It added that .mcp.json introduces further exposure through MCP configuration, warning that AI coding agents that rely heavily on project-level files could inadvertently grant shell access when a project is opened.

Terms & Concepts
  • git bundle: A single-file package of a Git repository that can include tracked data sent during repository transfer.
  • remote code execution: A security flaw that allows an attacker to run commands or code on another system.
  • MCP configuration: Project configuration settings that can shape how connected tools and permissions are handled.