npm

Headlines · 2

1. 14h
   Databricks injects domain knowledge into prompts to improve LLM npm malware triage

   A Databricks blog post describes findings and fixes from the LLM triage stage of its npm malware scanning pipeline. Collecting samples since November 2025, the team found that of 11,413 package-versions corroborated through OSV npm malware advisories, 96.2% hide their payload in the package source or fetch it from an external server, while only 3.8% (432 package-versions) bundle a binary. Those binary-bearing packages are the hardest to judge: among OSV-confirmed samples they failed to reach a decisive malicious verdict 14.4% of the time, more than double the 6.2% rate for source-only packages. The team built five adversarial Node.js native addon (.node) payload types covering credential theft, dropper/backdoor, reverse shell, cryptominer stub and persistence, with an obfuscation ladder running from a readable baseline to stripped symbols and single-byte XOR-encoded strings, in PE, ELF (all stripped) and Mach-O formats. Rather than fine-tuning models, they inject pre-computed static evidence into the prompt before inference, which they say improves detection quality for both budget and frontier models.

   Databricks Blog · 🔥 8
2. 4d
   SlugFest: npm Trusted Publishing flaw hit 1,500+ packages as AI agents raise risk

   Security firm Bloom Security disclosed a vulnerability dubbed SlugFest in npm Trusted Publishing: npm originally bound trust to a GitHub repository's human-readable slug rather than recording its permanent repository identifier, so once a repo is renamed, transferred or deleted, the old address can be claimed by someone else and satisfy the original trust configuration — granting publishing access without stealing the maintainer's credentials. A registry-wide scan found more than 1,500 vulnerable packages with over 10 million combined downloads and more than one million downloads per month, though Bloom notes these are only packages configured for Trusted Publishing. Bloom also measured AI-driven installs inside large enterprises, finding a typical endpoint receives roughly 70 agent-installed packages a month versus close to 350 on developer machines, and said it blocked one customer's AI agent from installing an affected package. npm implemented a fix before publication and confirmed the remediation; Bloom recommends storing immutable repository and owner identifiers and checking trust bindings after renames or transfers.

   The Next Web · 🔥 0

Experience and discussion from the community

Share my npm experienceAsk about npm