Skip to content
Security & Trust Talking point

GitHub researchers say attackers move to the gaps left after one supply chain link is hardened

A GitHub speaker said incidents trend toward the remaining gaps, so safe settings should be on from the start.

W
WebPulse Newsroom
AI-assisted · 2 min read
Share on X LinkedIn
GitHub researchers say attackers move to the gaps left after one supply chain link is hardened
In brief
  • A GitHub security speaker said incidents trend toward the gaps that remain after one part of the software supply chain is hardened.
  • The speaker argued that safe settings should be on by default, because small teams struggle to read thousands of pages of documentation.

GitHub security researchers say attackers move to the gaps that remain once one link in the software supply chain is hardened. A speaker on GitHub's show, in the episode "How GitHub secures open source" from GitHub Universe 2026, described that pattern. The supply chain is every step that carries code from a developer to the people who run it. The speaker's answer was secure defaults, not a longer checklist.

What was said

The speaker began with a plain claim: "every release path is also an attack path, right?" A release path is the route code takes to reach its users. Writing safe code is not enough, they said. Delivering it safely matters just as much.

They said attackers who were once less capable can now use frontier AI models. They are seeing supply chain attacks at an increasing pace. They pointed to a large attack on the npm ecosystem last year, and to many variants of it.

Then came the pattern. One project was hit in March through an upstream dependency, which the speaker thought was a scanner it relied on. Upstream means the compromise began in a tool the project trusted, not in its own code. The project then hardened its build and release pipeline and, the speaker said, did all the right things. A later incident surfaced in a different part of its infrastructure.

The speaker said settings are the hard part. A default setting is a protection that is already on when you start. A small team with no dedicated security person may struggle to read 12,000 pages of documentation. Those safe options, they argued, should simply be the defaults. They admitted the push meets resistance: "when you give someone a foot gun for a couple of years, they get really fond of it."

Why it matters

Our reading: a checklist protects only the links it names, and incidents show up at the link it left out. For managers, a better question is which steps that ship our code are safe by default.

The speaker described GitHub's own answer. Work on Actions, trusted publishing and staged publishing is meant to break the chain of events that carries an attack through. A GitHub CLI plugin also checks settings for branch protection, private vulnerability reporting, secret scanning, Dependabot and code scanning. Defaults ask far less expertise of a small team. Tightening one can still disrupt people who rely on the old behaviour.

A speaker on the show also said who should carry the cost: "security is the cost of consuming open source, right? It's not a tax that maintainers owe you."

The other side

The speakers work for GitHub, which sells the tools they described. The excerpts give no data showing that secure defaults reduce incidents. That attackers now use frontier models is their view, not a measured result. The March example is one anecdote, not proof of a rule.

The plugin they described audits settings, which is closer to a checklist run by a tool than to a true default. The conversation also left open whether defaults can keep pace with attackers who adapt.

Written by the WebPulse Newsroom with AI assistance, and checked by our editorial review: every quotation was verified against the recording's transcript. How we use AI.

The conversation this talking point comes from