SShortSingh.
Back to feed

Plugin4Shell RCE Flaw Hit 26,000 AI Coding Agents via Git Checkout Bypass

0
·72 views

Researchers at Air Security discovered in May 2026 that a zero-click remote code execution vulnerability, dubbed Plugin4Shell, affected Claude Code, OpenAI Codex, GitHub Copilot, and Google Gemini CLI. The flaw exploited a gap in how these agents handle plugin updates: they pin plugins to a specific git commit SHA but fail to verify the checked-out code actually matches that commit, allowing attackers to substitute malicious code via a branch named after the pinned SHA. A proof-of-concept plugin silently spread to over 26,000 agents before being removed, while a parallel campaign called SkillJacking hijacked 925 active skills and impacted 134,000 agents. Anthropic and OpenAI issued patches, but GitHub Copilot had not released a fix at the time of disclosure, and Google chose to deprecate Gemini CLI entirely rather than patch it. The incident highlights that AI coding agent plugin marketplaces have inherited the same supply chain attack risks as traditional package managers, with automatic background updates making exploitation especially stealthy.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Switch to digital delivery would make much of a software firm's physical logistics obsolete

A commentary by Stefan Priebsch on DEV Community argues that replacing a postal address with an email address is more than a data-field change. The example is a software company that moves from boxed physical products to digital delivery. The author contends that this shift eliminates whole stages of the traditional business process, including warehousing, packing, carrier handoff, and returns. Such a change, he suggests, makes older software architecture and its rules and dependencies obsolete as well. Fulfilment still matters, but it is reframed around downloads, licences, and access permissions.

0
ProgrammingDEV Community ·

Harness engineering : configurer l'environnement d'un agent IA plutôt que simplement le prompter

Un développeur en ESN, confronté à une application legacy, a découvert les agents IA et s'est attaché à comprendre leur fonctionnement. Il présente le concept de harness, c'est-à-dire l'ensemble des skills, MCP, outils et sous-agents qui entourent un LLM. Il distingue le harness interne fourni par défaut par le fournisseur, comme Google pour Gemini, du harness externe que l'utilisateur définit pour spécialiser l'agent. Il rappelle que cette pratique succède au prompt engineering et au context engineering, et que l'agent peut lui-même aider à configurer son harness. Enfin, il explique que le contexte, c'est-à-dire l'historique complet des échanges envoyé au LLM à chaque requête, constitue le concept central de ce travail.

0
ProgrammingDEV Community ·

Heat, not wiring, is often why LED strips fail early, and aluminum channels help

A DEV Community author argues that excessive heat is a common but overlooked cause of premature LED strip failure. Lifespan ratings are usually measured at about 25 degrees C in free air, while real installs mounted on wood, in ceilings, or behind diffusers can run at 50-60 degrees, sharply shortening life. Heat also speeds phosphor degradation, which causes dimming and color shift over time. The suggested remedy is an aluminum channel, which improves mounting contact and spreads heat, reportedly lowering strip temperature by 10-15 degrees, with extra measures like silicone bonding and a small air gap recommended for high-power or warm settings. The author notes that a simple touch test after prolonged operation can reveal overheating.

0
ProgrammingDEV Community ·

Building Fast Client-Side Calculation Engines: Architecture and Web Performance

Platforms offering instant online calculations aim for speed and mathematical accuracy, letting users get results without server round-trips or UI freezes. Running standard mathematical, financial, or engineering logic in the browser keeps response times under 10 milliseconds, and debounced inputs delay heavy computations until typing finishes. JavaScript's floating-point rounding errors can distort financial and scientific results, so developers may use fixed-point arithmetic or specialized math libraries and apply strict input validation with clear inline error messages. The article also recommends pairing each calculator with explanations of its formula and examples, and keeping layout shifts at zero so results appear without disrupting the page.