Developer Security | Think like an attacker, defend like a guardian

2026

On a near-black teal-blue background, a checkpoint gatehouse's fan-shaped scanning beam lights up geometric tokens on an inspection checklist one by one, while a document page and a permission card slip through a dark corridor beyond the beam's reach; in the foreground an open registry ledger lies perfectly blank — symbolizing the zero-prompt trust bypass caused by the folder-trust detection blind spot

Security Research

0day Hunting the Day After xAI Open-Sourced grok-build (Part 3): Grok-Build-CLI's folder-trust Blind Spot and the Zero-Prompt RCE

0day (3) I found the day after xAI open-sourced grok-build.

2026-07-18 15 min #AI Security

Over a near-black teal-blue background, a build instruction document disguised as a harmless project readme silently overrides an AI agent's command execution decisions, a command badge stamped read-only unleashes a build script executing arbitrary code with user privileges, system reconnaissance data spills through three parallel conduits from what appears to be a routine compile check — copper-orange accents punctuate the scene, symbolizing the Grok-Build-CLI cargo check RCE attack chain

Security Research

0day Hunting the Day After xAI Open-Sourced grok-build (Part 1): The cargo check RCE Chain in Grok-Build-CLI

0day (1) I found the day after xAI open-sourced grok-build.

2026-07-16 10 min #AI Security

On a near-black teal-blue background in copper-orange: a minimal configuration dissolving a permission fortress from within, a forged badge passing an inattentive checkpoint guard, a single skeleton key unlocking two vaults side by side

Security Research

0day Hunting the Day After xAI Open-Sourced grok-build (Part 2): The bypassPermissions RCE in Grok-Build-CLI and Claude Code CLI

0day (2) I found the day after xAI open-sourced grok-build.

2026-07-16 13 min #AI Security

Over a near-black teal-blue background, a captured git bundle unpacks within intercepted network traffic as plaintext credentials and cryptographic material spill out intact and ungoverned by any redaction filter; the foreground shows a clean developer-tool facade concealing a background upload conduit dispatching the entire repository ahead of the model's inference call; the midground features a parallel conduit bypassing a security filter with raw sensitive data flowing unchecked through the ungoverned channel — copper-orange accents punctuate the scene, symbolizing the Grok CLI whole-repo upload reverse analysis

Security Research

Grok CLI Whole-Repo Upload Reverse Analysis: How a Single Prompt Ships Your .env to the Cloud

Triple cross-verified with IDA Pro, Frida, and mitmproxy, this post reproduces Grok CLI v0.2.98 uploading the entire codebase (including .env, RSA private keys, and other common dev-time secrets) verbatim and unredacted to xAI cloud storage via git bundle at the start of each turn. Compared against v0.2.93, the upload mechanism is identical across both versions, respect_gitignore defaults to false, and one of the 8 independent switches allows remote override.

2026-07-15 10 min #Sample Analysis

2017

PHPUnit test file exposed as web RCE entry

Security Research

CVE-2017-9841 PHPUnit eval-stdin.php Remote Code Execution: When a PHP Testing Framework Becomes a Web Entry Point

CVE-2017-9841 is a pre-authentication remote code execution in PHPUnit's `eval-stdin.php` file, scored CVSS 9.8. The file is designed to accept PHP code through the CLI, but when the entire vendor directory is shipped to production it sits directly under the web root and turns a single unauthenticated POST into arbitrary code execution. The exposure pattern repeats across every PHP project that bundles dev dependencies into production: framework, CMS, package manager, or web root configuration. The fix is not just deleting the file — it is the six-piece baseline of delete + `composer --no-dev` + WAF block + periodic scan + CI/CD gate + yara rule, applied simultaneously.

2017-05-15 7 min #Vulnerability Analysis