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
CrowdSec kept a leaver's GitHub access open so he could finish some work, his laptop was hit by the TanStack npm compromise on May 11, and the repositories were copied on May 22 and posted to a forum on September 16.
Perspective Coverage
4 publishers
- Builder
- Builder 34%
- Operator
- Operator 51%
- Investor
- Investor 15%
Reality
- Evidence55
- Adoption
- Not scored
- Hype gap−25
- Incentives65
- Confidence58
buildOne report1 publisher One API call decides whether your SHA pin still means what it says
SHA pinning drew a clean line through the tj-actions compromise, and then Dependabot began bumping hashes faster than anyone could read them. The claim worth enforcing is the version comment that nothing verifies.
Reality
- Evidence62
- Adoption
- Not scored
- Hype gap+15
- Incentives40
- Confidence58
Google's undercover analyst watched TeamPCP poison packages from inside its core chat
Austin Larsen of Google's threat intelligence group says a Mandiant persona sat in TeamPCP's inner circle from almost the start of the campaign. For the companies the group breached, that infiltration was the warning system.
Reality
- Evidence55
- Adoption
- Not scored
- Hype gap+20
- Incentives60
- Confidence55
JFrog moves Xray's download blocking into a separately priced Curation seat by November 2026
JFrog is deprecating Xray's Block Download between April and November 2026 and moving enforcement into Curation, a product licensed per seat. Teams who use Xray as their gate have eight months to fund a replacement.
Reality
- Evidence35
- Adoption45
- Hype gap+35
- Incentives85
- Confidence40
buildOne report1 publisher GitHub lost 3,800 internal repos to code running with its editor's permissions
A dev.to writeup traces roughly 3,800 exfiltrated GitHub repositories to one trojanised Nx Console install from the official Marketplace, where the sandbox that would have contained it has been an open feature request since 2018.
Reality
- Evidence42
- Adoption28
- Hype gap+18
- Incentives62
- Confidence45
An ex-employee's live OAuth token let strangers copy 170 CrowdSec repositories in nine minutes
TeamPCP's npm compromise of TanStack reached CrowdSec through a departed employee's laptop, and the company learned its private repositories had been copied only when the code surfaced on a dark web forum in September.
Reality
- Evidence58
- Adoption55
- Hype gap+12
- Incentives72
- Confidence60
buildConfirmed2 publishers CrowdSec's final analysis puts the entry point in a former employee's development environment, hit by the TanStack npm malware in May. Its own organisation audit logs did not keep the clone events, so GitHub Support supplied them.
Publishers:dev.to · thearabianpost.com Reality
- Evidence62
- Adoption32
- Hype gap−8
- Incentives72
- Confidence58
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 A backdoored TanStack dependency lifted the CI key that could read CrowdSec's private repositories
TanStack closed out its package compromise on May 15th, and CrowdSec learned 124 days later that the same incident had cost it a CI credential with read access to its private code. The notice came from an outside researcher.
Reality
- Evidence46
- Adoption55
- Hype gap+12
- Incentives74
- Confidence55
buildOne report1 publisher A compromised TanStack pipeline signed 84 poisoned packages with valid provenance
Attestation proves a package came out of the pipeline it names. When the pipeline is the thing that was owned, the seal still verifies, and a gate that only checks origin passes all 84 versions pushed on May 11.
Reality
- Evidence45
- Adoption45
- Hype gap+12
- Incentives30
- Confidence50
buildOne report1 publisher A redundant dynamic import crashed every route at module load in the merged bundle
Both branches served fine on their own preview deployments. Nitro's second bundling pass over the merged server output split the namespace helper away from its call site into an import cycle, and the binding was undefined.
Reality
- Evidence62
- Adoption12
- Hype gap−5
- Incentives18
- Confidence58
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