buildOne report1 publisher Databricks' LLM triage stops short of a malicious verdict on 14.4% of npm malware that bundles a binary
Databricks says its LLM pipeline fails to reach a decisive malicious verdict on 14.4% of npm malware that bundles a binary, against 6.2% for source-only packages. Those binary packages are 432 of 11,413 scanned versions, and Databricks tests feeding the model pre-computed static evidence as the fix.
Reality
- Evidence50
- Adoption
- Not scored
- Hype gap+15
- Incentives60
- Confidence55
buildOne report1 publisher A fake recruiter's take-home ships an npm token that unlocks a package the public registry 404s
A developer says a fake-recruiter take-home bundled an npm token to fetch a hidden package, in a scheme a government advisory counts at 30,000+ machines. The author ran nothing and never read the hidden package, so its payload is inferred from structure.
Reality
- Evidence42
- Adoption
- Not scored
- Hype gap+20
- Incentives
- Not scored
- Confidence55
buildConfirmed2 publishers Tensorlake's npm SDK 0.5.144 carried a Shai-Hulud worm on October 8 that steals GitHub and npm tokens, cloud keys and AI coding-tool configs. A dev.to write-up of StepSecurity's teardown says revoking the stolen GitHub token triggers an rm -rf ~/, so the service must go first.
Publishers:dev.to · endorlabs.com Reality
- Evidence66
- Adoption
- Not scored
- Hype gap+30
- Incentives45
- Confidence62
buildOne report1 publisher Malicious npm package fires its loader from inside BTree.prototype.set()
Checkmarx found that indexed-btree declares no lifecycle hooks and starts its loader when application code calls set() with key 100. The loader reads its C2 address from a smart contract on Ethereum Sepolia.
Reality
- Evidence58
- Adoption38
- Hype gap+18
- Incentives62
- Confidence57
buildOne report1 publisher Eighteen flagged agent packages still install from npm weeks after the feeds listed them
AgentGate read the shipped code behind 30-plus OSV and GHSA flags, verified 19 npm packages as malicious, and found 18 still resolvable on publication day. Removal, not detection, is where the chain stopped.
Reality
- Evidence48
- Adoption20
- Hype gap+22
- Incentives78
- Confidence55
buildOne report1 publisher 1,400 npm maintainer domains, 18 flags, and one word doing too much work
A dev.to post scanned the domains behind the top 5,000 npm packages and found 18 with registration or email-security anomalies. The aggregate numbers matter more than the 18, and the headline overstates both.
Reality
- Evidence24
- Adoption
- Not scored
- Hype gap+58
- Incentives62
- Confidence30