A Coding Tool Was Quietly Uploading Your Git History
How this was made Verified AI
Every Intellegix briefing is generated from that day's broadcast and run through automated checks before it publishes — with a human paged on any flag. Here is the trail for this edition.
A post at ferstar.org detailed a finding about ZCode, a coding tool, that was silently uploading users' Git workspace snapshots to the cloud without explicit disclosure — earning 305 points and a hundred comments on Hacker News. The author captured network traffic and traced it to undocumented behavior, making this a technical finding rather than speculation. Git history is among the most sensitive data a developer handles: it contains code, commit messages, branch names, potentially credentials left in early commits, and proprietary algorithm implementations.
The Hacker News thread connected the finding to a pattern of AI-enhanced developer tools built primarily to showcase AI features rather than to meet enterprise security requirements, with practical advice emerging from the discussion: run any new coding tool in a sandboxed environment before connecting it to a real repository, monitor outbound network traffic during evaluation, and verify data handling documentation explicitly. Developer trust, once broken this way, travels quickly — through blog posts, through engineering Slack channels, through the Hacker News community itself — and is nearly impossible to rebuild.
At the opposite end of the sophistication spectrum, Ledger's hardware security lab published research on a photon-emission-guided laser fault injection attack against the RP2350, Raspberry Pi's newer microcontroller. The attack uses a laser to inject faults into the chip's secure debug path, guided by photon emission that reveals where computation is happening inside the silicon, ultimately bypassing secure boot and extracting protected firmware. The RP2350 was marketed with enhanced security features over its predecessor; Ledger's donjon team, whose core business involves finding implementation gaps in chips designed to be secure, found that 'secure' on a microcontroller means something considerably narrower than most hobbyist users assume.
The Rust language server protocol also drew attention this week, with a post from the rust-glancer project explaining why building a language server for Rust is substantially harder than for other languages. The core issue is architectural: Rust's borrow checker operates on a mid-level intermediate representation constructed after macro expansion, meaning the language server must understand a layer of semantic transformation that happens during compilation — breaking the assumption, standard in most LSP architectures, that parsing and analysis can proceed independently.