469 minus 189 is 280 paths added, a search radius about 2.5 times wider than the earlier builds of the same worm [4]. None of that widening requires an exploit. Each path is a file read on a host the operator already controls, which makes adding paths close to free and means the number goes up again in the next build.
What the number buys depends on what sits at the end of the chain. The reported sequence runs in steps: a token lifted from a developer workstation opens source code, that source code carries cloud credentials that open infrastructure, and a GitHub token grants write access to further repositories [6]. One credential class breaks that pattern. A package publishing token converts theft into distribution, because the build ships through a channel other developers and build systems consume automatically [7]. The rest of the chain moves an attacker sideways, but publishing authority moves the attack outward.
The sourcing behind the count deserves scrutiny. Both supplied copies of this report are the same thehackernews.com article [15]. The material carries no victim count and no list of compromised packages [16]. 469 measures the malware's search scope, and it says nothing about what was actually taken. The AI development tool configuration entry is the newest place teams are finding access keys [8], and on this evidence it is a collection target whose exploitation hasn't been confirmed.
The remedy aimed at the worst link is a token lifecycle change rather than another scanner. Short-lived verified authentication via OpenID Connect or similarly scoped mechanisms removes the standing publishing secret there is to steal, and the piece credits recent Docker and GitHub Actions updates with pushing trusted publishing in that direction [11][12]. Where a long-lived publishing token has to stay, it carries the blast radius of the packages it signs and should be inventoried on those terms [11]. Registry and dependency defense still does work; the ingredient a worm like this actually needs sits underneath it [14], in the standing authority that CI/CD, cloud tooling and now agent configuration keep on disk.
