Whatever your developers install without a ticket is now the thing that owns their laptop.
The Hacker News reported on October 30 that a trojanized version of Anthropic's official Claude Code extension went out through the Cursor Marketplace, dressed as a legitimate update, and tried to install a persistent SSH backdoor. The same day, SecurityWeek wrote that PHP2Shell attacks are rooting Palo Alto firewalls while failing against WordPress, with over 22.6 million exposed instances potentially affected by the critical PHP flaws. A day later, a security update 7.1.4 for WordPress landed and fixed 22 vulnerabilities impacting millions of sites.
One theme, told three ways: the update channel is the attack surface. A marketplace listing, an edge appliance and a CMS core all deliver code you did not write, on a schedule you do not control, into a trust boundary you never drew.
Most teams already handle CI dependencies this way, with pinned versions, reviewed diffs and narrow egress. Developer machines and editor extensions usually get none of that, even though they hold the keys to everything CI protects.
That is work we do: a security review of your developer and payment adjacent flows. We inventory what is actually installed, pin versions deliberately, and audit machines for leftover keys and authorized_keys entries that outlive the incident. It is a small, scoped engagement, and we come back to you with cost and timeline within a day.
If you run an engineering team, someone there should own the list of extensions your developers have installed. Probably nobody does.