buildOne report1 publisher npm worms ran attacker code from committed Claude Code hooks
Worms spreading through npm in May and June 2026 committed a SessionStart hook to .claude/settings.json that runs a script when Claude Code opens the repo. Removing the package leaves that file in place, a dev.to write-up says.
Reality
- Evidence55
- Adoption
- Not scored
- Hype gap−10
- Incentives
- Not scored
- Confidence55
Bloom Security finds 1,500 npm packages vulnerable to a publishing attack that needs no stolen credentials
Bloom Security found more than 1,500 npm packages, with over 10 million downloads, vulnerable to a publishing attack that needs no stolen credentials. Bloom also put AI-agent installs at about 70 packages a month on a typical endpoint, but its demonstration used only repositories its researchers controlled.
Reality
- Evidence50
- Adoption20
- Hype gap+25
- Incentives65
- Confidence45
buildConfirmed4 publishers Tensorlake's npm SDK 0.5.144 runs a credential-stealing worm from a preinstall hook at install time, Socket reported. According to Socket's analysis, any secret reachable from a workstation or build runner that installed the release may be exposed.
Perspective Coverage
4 publishers
- Builder
- Builder 44%
- Operator
- Operator 50%
- Investor
- Investor 6%
Reality
- Evidence74
- Adoption25
- Hype gap+10
- Incentives35
- Confidence72
buildOne report1 publisher The --config flag reopens a simple-git code-execution bug that was patched in 2022
CVE-2026-6951 reopens remote code execution in simple-git, a library downloaded 8.7 million times a week, by respelling the blocked -c flag as --config. The 2022 patch never checked the long form, so the same attack works wherever untrusted input reaches a git call.
Reality
- Evidence55
- Adoption45
- Hype gap+10
- Incentives20
- Confidence45
buildOne report1 publisher A predictable pnpm cache key carried fork code into TanStack's npm release workflow
TanStack's postmortem says 84 malicious versions went out across 42 packages on 2026-05-11 with no npm token stolen, because a release job restored a cache that an untrusted pull_request_target build had written.
Publishers:tanstack.com
Reality
- Evidence68
- Adoption45
- Hype gap+6
- Incentives65
- Confidence58
buildOne report1 publisher ChainDrop executes from a checked-in agent config the moment a coding session starts
GitGuardian says the ChainDrop worm reached 444 npm packages by planting a SessionStart hook in Claude Code and a folderOpen task in VS Code, and the publishing credential it steals is used to republish inside the same session.
Reality
- Evidence45
- Adoption55
- Hype gap+22
- Incentives80
- Confidence42
buildOne report1 publisher The Mini Shai-Hulud worm passed provenance checks by running inside the release pipeline
Akamai says the May 11-12 wave poisoned a CI cache and minted publish credentials from inside a trusted build, so the attestation it produced was honest. Any gate that only checks for provenance would have passed it.
Reality
- Evidence38
- Adoption33
- Hype gap+9
- Incentives74
- Confidence44