# npm packages

npm packages are files or directories described by package.json files and published to the npm registry; they commonly contain Node.js modules.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Node2Shell: Your SBOMs Already Know Which Node.js Builds You're Running

DevFeed: [Node2Shell: Your SBOMs Already Know Which Node.js Builds You're Running](<https://devfeed.tech/articles/node2shell-your-sboms-already-know-which-node-js-builds-you-re-running-144733.md>)

Original publisher: [Read original article](<https://anchore.com/blog/node2shell-your-sboms-already-know-which-nodejs-builds-youre-running/>)

Author: Dalton Bunn

Published: 2026-11-13T13:00:00Z

Content type: article

Language: en

Sources: [Anchore](<https://devfeed.tech/sources/anchore.md>)

Topics: [Node.js](<https://devfeed.tech/topics/node-js.md>), [Bun](<https://devfeed.tech/topics/bun.md>), [Python](<https://devfeed.tech/topics/python.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [anchore](<https://devfeed.tech/tags/anchore.md>), [audit](<https://devfeed.tech/tags/audit.md>), [binaries](<https://devfeed.tech/tags/binaries.md>), [blog](<https://devfeed.tech/tags/blog.md>), [brotli](<https://devfeed.tech/tags/brotli.md>), [brotli-decoder](<https://devfeed.tech/tags/brotli-decoder.md>), [builds](<https://devfeed.tech/tags/builds.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [decoder](<https://devfeed.tech/tags/decoder.md>), [first](<https://devfeed.tech/tags/first.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [json](<https://devfeed.tech/tags/json.md>), [know](<https://devfeed.tech/tags/know.md>), [layer](<https://devfeed.tech/tags/layer.md>), [library](<https://devfeed.tech/tags/library.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [node2shell](<https://devfeed.tech/tags/node2shell.md>), [running](<https://devfeed.tech/tags/running.md>), [sbom](<https://devfeed.tech/tags/sbom.md>), [sboms](<https://devfeed.tech/tags/sboms.md>), [software-supply-chain-security](<https://devfeed.tech/tags/software-supply-chain-security.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

Node2Shell affects Brotli code embedded in Node.js runtimes, so package lockfiles and npm audit do not identify affected runtime binaries. A crafted Brotli stream can overflow an internal buffer, causing a crash or potentially code execution as the Node.js process user. Exposure can occur through built-in fetch() response decoding and, with Express 5 and body-parser 2.x, default Brotli request-body inflation. The excerpt describes Anchore Enterprise identifying compiled Node.js versions as binary packages and querying stored SBOMs after vulnerability feeds update, without rescanning; distro-installed Node.js is handled through its system Brotli package and distro advisories. Its Kubernetes inventory agent tracks running workloads by image digest, helping find pods still using vulnerable builds after tags move. The stated fixed lines are 26.12.1, 24.22.1, and 22.23.4; end-of-life Node.js lines will not receive upstream fixes.

### Source excerpt

The post Node2Shell: Your SBOMs Already Know Which Node.js Builds You're Running appeared first on Anchore.When a critical CVE lands in a JavaScript library, the first hours of a response go into reading lockfiles. Node2Shell sits one layer below them. The vulnerable Brotli decoder is compiled into the Node.js runtime itself, under deps/brotli, so package-lock.json and npm audit have nothing to report. The questions that matter are which node binaries [...]

## Automating Contract Signing in Node.js: Webhooks, Verification, and Storing Signed PDFs

DevFeed: [Automating Contract Signing in Node.js: Webhooks, Verification, and Storing Signed PDFs](<https://devfeed.tech/articles/automating-contract-signing-in-node-js-webhooks-verification-and-storing-signed-pdfs-133706.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/automating-contract-signing-in-node-js-webhooks-verification-and-storing-signed-pdfs/>)

Author: SitePoint Team

Published: 2026-11-13T10:50:38Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [Database](<https://devfeed.tech/topics/database.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>)

Tags: [node-js](<https://devfeed.tech/tags/node-js.md>), [pdfs](<https://devfeed.tech/tags/pdfs.md>), [signing](<https://devfeed.tech/tags/signing.md>), [verification](<https://devfeed.tech/tags/verification.md>), [webhooks](<https://devfeed.tech/tags/webhooks.md>)

### AI overview

The tutorial builds a Node.js/Express signing workflow around Firma.dev: send a template-based request, receive completion webhooks, verify HMAC signatures over the raw request bytes with a timestamp tolerance, deduplicate event IDs, then fetch and store the signed PDF and audit trail. It recommends acknowledging events quickly and using a durable queue in production; the tutorial's setImmediate demo can lose work if the process exits after acknowledging. Downloads may return 503 while files are generated, so the API client honors Retry-After for 429 and 503 responses. Because webhook retries are finite and events may be missed or unordered, a scheduled status reconciliation job checks pending requests. The overview also notes short-lived download URLs, provider-specific retry behavior, and that signature headers and event details vary across providers.

### Source excerpt

null Continue reading Automating Contract Signing in Node.js: Webhooks, Verification, and Storing Signed PDFs on SitePoint.

## pnpm 11.28.12

DevFeed: [pnpm 11.28.12](<https://devfeed.tech/articles/pnpm-11-28-12-133525.md>)

Original publisher: [Read original article](<https://pnpm.io/blog/releases/11.28.12>)

Author: Zoltan Kochan

Published: 2026-11-13T00:00:00Z

Content type: release

Language: en

Sources: [pnpm](<https://devfeed.tech/sources/pnpm-blog.md>)

Topics: [pnpm](<https://devfeed.tech/topics/pnpm.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>)

Tags: [catalog](<https://devfeed.tech/tags/catalog.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [node](<https://devfeed.tech/tags/node.md>), [peer](<https://devfeed.tech/tags/peer.md>), [pnpm](<https://devfeed.tech/tags/pnpm.md>), [registry](<https://devfeed.tech/tags/registry.md>), [security](<https://devfeed.tech/tags/security.md>), [url](<https://devfeed.tech/tags/url.md>)

### AI overview

pnpm 11.28.12 fixes broad install and deployment issues, including frozen-lockfile failures, unstable peer provider selection, sparse-checkout and hoisted-linker behavior, and `pnpm deploy` handling of workspace packages and offline lockfile reuse. It also closes a registry-routing safety gap: `${VAR}` placeholders in registry URLs in `pnpm-workspace.yaml` or `.npmrc` now fail the command because pnpm does not expand them, instead of allowing resolution from another registry. Remote resolution and shared build caches require pnpr 0.1.0-alpha.20 or later, whose advertised capabilities must confirm the requested policies. The release also updates bundled `node-gyp` to remove the flagged undici 6 version and fixes its proxy/custom CA behavior on Node.js 26. Other changes cover peer dependency correctness, runtime engine checks, build scripts, bins, and command behavior.

### Source excerpt

pnpm 11.28.12 fixes many peer dependency, pnpm deploy, frozen-lockfile, and nodeLinker: hoisted bugs. It also includes a security fix. A ${VAR} placeholder in a repository's registry URL now fails the command, so pnpm no longer sends those requests to another registry. The bundled node-gyp no...

## Vercel Sandbox now supports managed npm credentials

DevFeed: [Vercel Sandbox now supports managed npm credentials](<https://devfeed.tech/articles/vercel-sandbox-now-supports-managed-npm-credentials-133482.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-sandbox-now-supports-managed-npm-credentials>)

Author: Elisabeth Rülke

Published: 2026-11-12T01:56:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [npm](<https://devfeed.tech/topics/npm.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Environment Variables](<https://devfeed.tech/topics/environment-variables.md>), [jfrog artifactory](<https://devfeed.tech/topics/jfrog-artifactory.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [artifactory](<https://devfeed.tech/tags/artifactory.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cli](<https://devfeed.tech/tags/cli.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [github-packages](<https://devfeed.tech/tags/github-packages.md>), [install](<https://devfeed.tech/tags/install.md>), [jfrog-artifactory](<https://devfeed.tech/tags/jfrog-artifactory.md>), [latest](<https://devfeed.tech/tags/latest.md>), [managed](<https://devfeed.tech/tags/managed.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-packages](<https://devfeed.tech/tags/npm-packages.md>), [packages](<https://devfeed.tech/tags/packages.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel Sandbox can install private npm packages using credentials stored in team Shared Environment Variables, including from custom registries such as GitHub Packages and JFrog Artifactory. Set `credentials: { npm: true }` when creating a sandbox, then run the package install after placing project files in its working directory. Tokens stay outside the sandbox; the firewall authenticates install requests to configured registries so a coding agent can install dependencies without seeing the tokens. Update the Sandbox SDK or CLI to the latest version.

### Source excerpt

Vercel Sandbox can now install your team's private npm packages using credentials stored in team Shared Environment Variables. Custom registries such as GitHub Packages and JFrog Artifactory are also supported. Pass credentials: { npm: true } when creating a sandbox to let it use your team's existing npm credentials. Tokens stay outside the sandbox. The firewall adds authentication to install requests sent to your configured registries, so a coding agent can install dependencies without seeing the tokens. Update your Sandbox SDK or CLI to the latest version. Read the npm credentials documentation to get started. Read more

## Releases as Code

DevFeed: [Releases as Code](<https://devfeed.tech/articles/releases-as-code-132578.md>)

Original publisher: [Read original article](<https://code.dblock.org/2026/11/12/releases-as-code.html>)

Author: Daniel Doubrovkine (dblock@dblock.org)

Published: 2026-11-12T00:00:00Z

Content type: article

Language: en

Sources: [Daniel Doubrovkine](<https://devfeed.tech/sources/daniel-doubrovkine.md>)

Topics: [releases](<https://devfeed.tech/topics/releases.md>), [Ruby](<https://devfeed.tech/topics/ruby.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [version-control](<https://devfeed.tech/topics/version-control.md>)

Tags: [automate](<https://devfeed.tech/tags/automate.md>), [code](<https://devfeed.tech/tags/code.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [language](<https://devfeed.tech/tags/language.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [npm](<https://devfeed.tech/tags/npm.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [readme](<https://devfeed.tech/tags/readme.md>), [release](<https://devfeed.tech/tags/release.md>), [release-workflow](<https://devfeed.tech/tags/release-workflow.md>), [releases](<https://devfeed.tech/tags/releases.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [rust](<https://devfeed.tech/tags/rust.md>), [stable](<https://devfeed.tech/tags/stable.md>), [tag](<https://devfeed.tech/tags/tag.md>), [test](<https://devfeed.tech/tags/test.md>), [test-it](<https://devfeed.tech/tags/test-it.md>), [testing](<https://devfeed.tech/tags/testing.md>), [updating](<https://devfeed.tech/tags/updating.md>)

### AI overview

The article argues that release workflows should be treated as testable project code because a partial failure can leave published packages, tags, or development versions inconsistent. It describes npm-package-release, ruby-gem-release, and rust-crate-release, showing lifecycle hooks that update a README's "Release Status" section to identify the stable version at the release tag and the next version on the development branch. Each example tests the actual workflow with project fixtures and checks both versions. The author reports that adopting shared libraries reduced release-related JavaScript and Ruby code by 66% across four cited projects; the excerpt also names projects using the three libraries.

### Source excerpt

A release needs to be reliable, which means it needs to be testable. A typical release selects a version, updates a changelog, builds an artifact, creates a commit and a tag, publishes the package, creates a GitHub Release, and often prepares the next development version. Projects add their own steps, such as updating version references in documentation, and these steps need to agree on what was released. If one breaks, the release fails halfway through, leaving a published package without a matching tag or a development version that wasn't updated. You can't always undo a published package and start over. Test your release code. Releases Are Software I've spent plenty of time maintaining release instructions, shell scripts, and GitHub Actions YAML. They automate the work, but the interesting logic tends to be spread across commands that are hard to exercise without actually making a release. I wanted to treat a release workflow like the rest of the project: write it in code, customize it in code, and test the behavior that matters. This idea has become a family of libraries: npm-package-release, ruby-gem-release, and rust-crate-release. Each brings the workflow into the language of the project it releases. For example, a project's README on the default branch may describe features that haven't been released yet. Grape's README identifies the upcoming version and links to the stable release so users don't confuse the two. After a release, I want the development README to say "You're reading the documentation for the next release, v1.2.3." The README at the release tag should identify the stable version instead. I could do this with a shell script that searches and replaces text, then hope it still works the next time I release. Instead, I can write the release logic in the project's language and test it. Updating the README These examples assume a ## Release Status section in README.md. Each replaces that section during release preparation and again when preparing t

## pnpm 12.20.0

DevFeed: [pnpm 12.20.0](<https://devfeed.tech/articles/pnpm-12-20-0-129757.md>)

Original publisher: [Read original article](<https://pnpm.io/blog/releases/12.20.0>)

Author: Zoltan Kochan

Published: 2026-11-12T00:00:00Z

Content type: release

Language: en

Sources: [pnpm](<https://devfeed.tech/sources/pnpm-blog.md>)

Topics: [pnpm](<https://devfeed.tech/topics/pnpm.md>), [Dependency management](<https://devfeed.tech/topics/dependency-management.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [software dark matter](<https://devfeed.tech/topics/software-dark-matter.md>)

Tags: [2-0-0](<https://devfeed.tech/tags/2-0-0.md>), [after](<https://devfeed.tech/tags/after.md>), [all](<https://devfeed.tech/tags/all.md>), [alpha](<https://devfeed.tech/tags/alpha.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [build](<https://devfeed.tech/tags/build.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [directory](<https://devfeed.tech/tags/directory.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [flag](<https://devfeed.tech/tags/flag.md>), [local](<https://devfeed.tech/tags/local.md>), [node](<https://devfeed.tech/tags/node.md>), [peer](<https://devfeed.tech/tags/peer.md>), [pnpm](<https://devfeed.tech/tags/pnpm.md>), [records](<https://devfeed.tech/tags/records.md>), [remote](<https://devfeed.tech/tags/remote.md>), [scanners](<https://devfeed.tech/tags/scanners.md>), [security](<https://devfeed.tech/tags/security.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

pnpm 12.20.0 adds local directory dependency specifiers to experimental v13 lockfiles; frozen installs now reject changed specifiers even if the locked versions still satisfy them. Remote resolution, shared build caches, and release notes require pnpr servers that advertise and confirm the requested policies, and no longer support pnpr 0.1.0-alpha.19 or older. Dependency fixes cover catalog-aware overrides, npm-style `::` Git fragments, runtime-version preservation during dedupe, and peer handling. With `nodeLinker: hoisted`, packages retain nested dependency copies when their resolved version differs from the top-level one. Lockfile and peer-graph fixes address stale bindings, cycles, optionality, and injected workspace packages. The release also removes flagged undici 6 from bundled `node-gyp` and fixes proxy or custom-CA downloads on Node.js 26, alongside script cleanup, TLS, registry, SBOM, and store-status fixes.

### Source excerpt

pnpm 12.20.0 records the specifiers of local directory dependencies in the experimental v13 lockfile and fixes several nodeLinker: hoisted, peer dependency, and overrides bugs. The bundled node-gyp no longer ships the undici version that security scanners flag. Remote resolution and shared build...

## How to Build an MCP Server That Checks npm Packages Before AI Installs Them

DevFeed: [How to Build an MCP Server That Checks npm Packages Before AI Installs Them](<https://devfeed.tech/articles/how-to-build-an-mcp-server-that-checks-npm-packages-before-ai-installs-them-128451.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-to-build-an-mcp-server-that-checks-npm-packages-before-ai-installs-them?source=rss>)

Author: Tarun Singh

Published: 2026-11-11T07:39:09Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [Cloudflare Workers](<https://devfeed.tech/topics/cloudflare-workers.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [audit](<https://devfeed.tech/tags/audit.md>), [build](<https://devfeed.tech/tags/build.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [cloudflare-workers](<https://devfeed.tech/tags/cloudflare-workers.md>), [deprecation](<https://devfeed.tech/tags/deprecation.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-packages](<https://devfeed.tech/tags/npm-packages.md>), [packages](<https://devfeed.tech/tags/packages.md>), [remote](<https://devfeed.tech/tags/remote.md>), [remote-mcp-server](<https://devfeed.tech/tags/remote-mcp-server.md>), [server](<https://devfeed.tech/tags/server.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

The article builds pkgscout, a stateless MCP server on Cloudflare Workers that checks npm packages before an AI suggests installing them. Its `inspect_package` tool reports package metadata and deprecation, and generates bounded typo variants when a name is missing; npm search can bury deprecated packages, while typo matches may themselves be misleading or malicious, so suggestions include warnings. `check_vulnerabilities` queries npm's advisory database but requires exact versions, rejecting ranges. To stay within Workers' 10 ms CPU limit, the server fetches compact `/latest` manifests instead of large package documents and caches registry calls for five minutes. The excerpt also explains bearer-token authentication, local testing with the SDK's modern protocol negotiation, and deployment. It describes a shared token as suitable for personal use and points to OAuth for team sharing; PyPI support and checks for newly created packages remain proposed additions.

### Source excerpt

Build a remote MCP server on Cloudflare Workers that checks npm packages for typos, deprecation and known vulnerabilities before your AI installs them.

## Introducing JFrog Threat Hub: Turning Vulnerability Intelligence into Blast Radius Analysis

DevFeed: [Introducing JFrog Threat Hub: Turning Vulnerability Intelligence into Blast Radius Analysis](<https://devfeed.tech/articles/introducing-jfrog-threat-hub-turning-vulnerability-intelligence-into-blast-radius-analysis-126405.md>)

Original publisher: [Read original article](<https://jfrog.com/blog/threat-hub-turns-vulnerability-intelligence-into-blast-radius-analysis/>)

Author: drewt@jfrog.com

Published: 2026-11-10T14:26:26Z

Content type: article

Language: en

Sources: [From the Frog's mouth - JFrog Blog](<https://devfeed.tech/sources/from-the-frog-s-mouth-jfrog-blog.md>)

Topics: [Jfrog](<https://devfeed.tech/topics/jfrog.md>), [Threat Hunting & Intel](<https://devfeed.tech/topics/threat-hunting-intel.md>), [jfrog xray](<https://devfeed.tech/topics/jfrog-xray.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [OSINT](<https://devfeed.tech/topics/osint.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [DevSecOps](<https://devfeed.tech/topics/devsecops.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [hugging face](<https://devfeed.tech/topics/hugging-face.md>)

Tags: [attack](<https://devfeed.tech/tags/attack.md>), [awareness](<https://devfeed.tech/tags/awareness.md>), [blast-radius](<https://devfeed.tech/tags/blast-radius.md>), [blast-radius-analysis](<https://devfeed.tech/tags/blast-radius-analysis.md>), [cve](<https://devfeed.tech/tags/cve.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [hugging-face](<https://devfeed.tech/tags/hugging-face.md>), [intelligence](<https://devfeed.tech/tags/intelligence.md>), [jfrog](<https://devfeed.tech/tags/jfrog.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [npm](<https://devfeed.tech/tags/npm.md>), [package](<https://devfeed.tech/tags/package.md>), [pypi](<https://devfeed.tech/tags/pypi.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [supply-chain-attack](<https://devfeed.tech/tags/supply-chain-attack.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>), [threat-intelligence](<https://devfeed.tech/tags/threat-intelligence.md>), [trending](<https://devfeed.tech/tags/trending.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

JFrog Threat Hub combines a daily-updated feed of vetted security research and external advisories with an impact search in JFrog Xray. For supported CVE and malicious-package posts, Check Impact searches the organization's scanned artifacts and reports matches with repository, vulnerable component version, scan date, and runtime status, helping teams scope exposure and prioritize remediation in one workflow. Posts include source, date, tags, and affected-package labels; some also show a severity mismatch when JFrog Research's assessment differs from the published score. The text says JFrog's research monitors npm, PyPI, and Hugging Face and assesses real-world exploitability. Impact results can be exported, used to set Xray policies, or sent into triage. The described search applies to supported posts and scanned artifacts.

### Source excerpt

A new supply chain attack hits the news. A CVE with a dramatic name starts trending. A malicious package turns up in npm, PyPI, and Hugging Face. Within minutes, your Slack channels fill up, your CISO wants an update, and someone asks the question every DevSecOps professional dreads: "How are we affected?" Providing a definitive ...

## New in Symfony 8.2: AssetMapper Improvements

DevFeed: [New in Symfony 8.2: AssetMapper Improvements](<https://devfeed.tech/articles/new-in-symfony-8-2-assetmapper-improvements-127158.md>)

Original publisher: [Read original article](<https://symfony.com/blog/new-in-symfony-8-2-assetmapper-improvements>)

Author: Javier Eguiluz

Published: 2026-11-10T08:14:00Z

Content type: release

Language: en

Sources: [Symfony](<https://devfeed.tech/sources/symfony-blog.md>)

Topics: [Symfony](<https://devfeed.tech/topics/symfony.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [import](<https://devfeed.tech/topics/import.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>)

Tags: [asset](<https://devfeed.tech/tags/asset.md>), [asset-map](<https://devfeed.tech/tags/asset-map.md>), [assets](<https://devfeed.tech/tags/assets.md>), [css](<https://devfeed.tech/tags/css.md>), [development](<https://devfeed.tech/tags/development.md>), [directory](<https://devfeed.tech/tags/directory.md>), [esm](<https://devfeed.tech/tags/esm.md>), [feature](<https://devfeed.tech/tags/feature.md>), [files](<https://devfeed.tech/tags/files.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [map](<https://devfeed.tech/tags/map.md>), [maps](<https://devfeed.tech/tags/maps.md>), [security](<https://devfeed.tech/tags/security.md>), [symfony](<https://devfeed.tech/tags/symfony.md>), [third-party](<https://devfeed.tech/tags/third-party.md>)

### AI overview

Symfony 8.2 adds AssetMapper controls for package integrity, version timing, import-map exposure and compiled metadata. Configurable SHA-256, SHA-384 or SHA-512 hashes add SRI attributes to rendered resources. `minimum_release_age` makes `importmap:update` hold back newer releases, prereleases and versions above `latest`; `importmap:outdated` lists withheld versions. It does not restrict `importmap:require`, and checking publication dates requires downloading larger npm metadata. The new `--no-esm` option fetches a package file as published, but requires its in-package path; relative imports are fetched while bare imports must still be required separately. In debug mode, AssetMapper now ignores compiled metadata so source edits are used. Setting `importmap_entries: reachable` limits rendered entries to those reachable through static and dynamic imports, but cannot trace variable dynamic imports and is disabled by default. `metadata_dir` can move generated metadata outside the public assets directory; its default remains unchanged.

### Source excerpt

AssetMapper lets you use modern JavaScript and CSS without a build step, relying on native browser features like import maps. Symfony 8.2 improves it in several areas: security of third-party packages, control over what the import map exposes, and a smoother...

## The Range Shrinks, the Threat Remains: Re-evaluating LLM Package Hallucinations on the 2026 Frontier-Model Cohort

DevFeed: [The Range Shrinks, the Threat Remains: Re-evaluating LLM Package Hallucinations on the 2026 Frontier-Model Cohort](<https://devfeed.tech/articles/the-range-shrinks-the-threat-remains-re-evaluating-llm-package-hallucinations-on-the-2026-frontier-model-cohort-126883.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2605.17062>)

Author: Aleksandr Churilov (Independent Researcher)

Published: 2026-11-10T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [PyPI](<https://devfeed.tech/topics/pypi.md>), [Hallucination detection](<https://devfeed.tech/topics/hallucination-detection.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [Frontier Model](<https://devfeed.tech/topics/frontier-model.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [frontier](<https://devfeed.tech/tags/frontier.md>), [frontier-model](<https://devfeed.tech/tags/frontier-model.md>), [hallucinations](<https://devfeed.tech/tags/hallucinations.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [llm](<https://devfeed.tech/tags/llm.md>), [malware](<https://devfeed.tech/tags/malware.md>), [model](<https://devfeed.tech/tags/model.md>), [npm](<https://devfeed.tech/tags/npm.md>), [package](<https://devfeed.tech/tags/package.md>), [pypi](<https://devfeed.tech/tags/pypi.md>), [python](<https://devfeed.tech/tags/python.md>), [registries](<https://devfeed.tech/tags/registries.md>), [slopsquatting](<https://devfeed.tech/tags/slopsquatting.md>)

### AI overview

Across five 2026 frontier models and 199,840 Python and JavaScript generations, nonexistent package names appeared in 3.6-5.0% of package mentions (2.2-3.4% of generations), roughly matching 2024 commercial models; Python rates exceeded JavaScript rates for every model. A preregistered recheck against live PyPI and npm registries found 104 names hallucinated by all five models, down from 127 previously reported; 26 earlier entries were valid imports whose module and package names differ. Accidental six-month exposure of the researchers' list showed no detectable increase in registration: about 1% of hallucinated names were registered, at similar rates for exposed and unexposed names, with the 95% interval ruling out increases above 2.5 percentage points. The risk remains: at least 23 suggested package names had previously hosted malware, and one hallucinated name was registered with malware after the study runs.

### Source excerpt

arXiv:2605.17062v4 Announce Type: replace Abstract: Package hallucinations, LLM-generated references to packages that do not exist, enable slopsquatting: an attacker registers the hallucinated name. We replicate Spracklen et al. (USENIX Security '25) on five 2026 frontier models over 199,840 Python and JavaScript generations. This version reports a preregistered live revalidation that replaces the static package lists of earlier versions with two independent checks against the live PyPI and npm registries. Hallucination rates are 3.6-5.0% of package mentions (2.2-3.4% of generations): the 2026 frontier sits at the level of 2024's commercial models, and the open-weight gap seen in 2024 has disappeared. Python exceeds JavaScript for every model. The set of names hallucinated by all five models shrinks from the 127 reported earlier to 104; 26 earlier entries were correct import statements whose module name differs from the package name. Using the accidental six-month public exposure of our own list as a natural experiment, we find no detectable effect of publication: about 1% of hallucinated names were registered within six months, at the same rate for published and unpublished names, and the 95% interval excludes increases above 2.5 percentage points. Still, at least 23 package names that the models suggest had previously hosted malware later removed by the registries, and one hallucinated name was registered with malware after our runs.

## Announcing the OpenTelemetry JavaScript SDK 3.0

DevFeed: [Announcing the OpenTelemetry JavaScript SDK 3.0](<https://devfeed.tech/articles/announcing-the-opentelemetry-javascript-sdk-3-0-119945.md>)

Original publisher: [Read original article](<https://opentelemetry.io/blog/2026/otel-js-sdk-3-0/>)

Author: OpenTelemetry Authors; Docs CC BY

Published: 2026-11-05T15:54:08Z

Content type: release

Language: en

Sources: [OpenTelemetry](<https://devfeed.tech/sources/blog-on-opentelemetry.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [CommonJS](<https://devfeed.tech/topics/commonjs.md>), [export](<https://devfeed.tech/topics/export.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [api](<https://devfeed.tech/tags/api.md>), [can](<https://devfeed.tech/tags/can.md>), [changes](<https://devfeed.tech/tags/changes.md>), [details](<https://devfeed.tech/tags/details.md>), [except](<https://devfeed.tech/tags/except.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [found](<https://devfeed.tech/tags/found.md>), [full](<https://devfeed.tech/tags/full.md>), [guide](<https://devfeed.tech/tags/guide.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [javascript-packages](<https://devfeed.tech/tags/javascript-packages.md>), [js](<https://devfeed.tech/tags/js.md>), [js-sdk](<https://devfeed.tech/tags/js-sdk.md>), [list](<https://devfeed.tech/tags/list.md>), [major](<https://devfeed.tech/tags/major.md>), [migration](<https://devfeed.tech/tags/migration.md>), [migration-guide](<https://devfeed.tech/tags/migration-guide.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [sdk](<https://devfeed.tech/tags/sdk.md>)

### AI overview

OpenTelemetry JavaScript SDK 3.0 raises the minimum supported Node.js version to 22.15.0, dropping Node.js 18 and 20, and provides proper ESM and CommonJS exports. Stable SDK packages are version 3.0.0 or later; experimental packages are 0.300.0 or later. The release adds complex attributes in some API areas, stabilizes Logs and folds `@opentelemetry/api-logs` into `@opentelemetry/api`, consolidates tracing packages into `@opentelemetry/sdk-trace`, and removes deprecated packages. Several public types and class names changed, though the API package has no breaking changes; users of `@opentelemetry/auto-instrumentations-node` following the zero-code instructions need no changes. Stable SDK 2.x packages are supported for one year from the 3.0.0 release. Consult the migration guide for the complete package list and migration details.

### Source excerpt

OpenTelemetry JavaScript has released SDK 3.0 (stable v3.0.0 packages and experimental v0.300.0 packages) and API 1.10.0. Migration guide For a detailed description of breaking changes, see the OpenTelemetry JS SDK 3.x migration guide. What is JS SDK 3.x? JS SDK 3.x encompasses new releases of the @opentelemetry/* JavaScript packages published from the opentelemetry-js repository, except the API and semantic-conventions packages. The package versions for this new major will be >=3.0.0 for the stable and >=0.300.0 for the unstable packages. Details on the full list of packages can be found in the migration guide.

## X.js: A Live Benchmark for Node.js Taint-Style Vulnerabilities

DevFeed: [X.js: A Live Benchmark for Node.js Taint-Style Vulnerabilities](<https://devfeed.tech/articles/x-js-a-live-benchmark-for-node-js-taint-style-vulnerabilities-118043.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.18585>)

Author: Jos\\'e Afonso, Jo\\~ao Madeira Pereira, Ronghao Ni, Limin Jia, Jos\\'e Fragoso Santos, Pedro Ad\\~ao

Published: 2026-11-05T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [code security](<https://devfeed.tech/topics/code-security.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [command-injection](<https://devfeed.tech/tags/command-injection.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [datasets](<https://devfeed.tech/tags/datasets.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [execution](<https://devfeed.tech/tags/execution.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [exploits](<https://devfeed.tech/tags/exploits.md>), [github-advisory-database](<https://devfeed.tech/tags/github-advisory-database.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [js](<https://devfeed.tech/tags/js.md>), [live](<https://devfeed.tech/tags/live.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-packages](<https://devfeed.tech/tags/npm-packages.md>), [package](<https://devfeed.tech/tags/package.md>), [path-traversal](<https://devfeed.tech/tags/path-traversal.md>), [pollution](<https://devfeed.tech/tags/pollution.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

X.js is a live benchmark for evaluating research on Node.js taint-style vulnerabilities, addressing the gap left by datasets that stop in 2022. It covers code and command injection, prototype pollution, and path traversal. From 1,738 advisories collected through mid-2026, it provides source and sink locations, validated executable exploits with traces, and patched package versions when available. Dependencies are mirrored in a self-hosted registry, and infrastructure generates and validates exploits for newly reported vulnerabilities. The current release contains 1,159 validated exploits across 965 packages. Its analysis finds that the median size of vulnerable packages grew from about 250 lines of code in 2021-2022 to 6,100 in 2026.

### Source excerpt

arXiv:2610.18585v3 Announce Type: replace-cross Abstract: JavaScript vulnerabilities in npm packages pose a significant risk to the Node$.$js ecosystem, and a growing body of work aims to detect, exploit, and mitigate them. Studying and evaluating this work requires up-to-date collections of real vulnerabilities, yet the most commonly used datasets stop recording vulnerabilities in 2022. We present X$.$js, a live benchmark of real-world Node$.$js taint-style vulnerabilities covering code and command injection, prototype pollution, and path traversal. Built from 1,738 advisories collected through mid-2026, primarily from the GitHub Advisory Database, X$.$js pairs each vulnerability with precise source and sink locations, a validated executable exploit and its execution trace, and, when available, a patched version of the package. X$.$js supports long-term reproducibility and growth: dependencies are mirrored in a self-hosted registry to guard against package removal from the ecosystem, and dedicated infrastructure generates and validates exploits for newly reported vulnerabilities. The current release contains 1,159 validated exploits for 965 packages. Using X$.$js, we characterize how the frequency, structure, and complexity of Node$.$js taint-style vulnerabilities have evolved over time. We find that these vulnerabilities are increasingly reported in large packages: the median vulnerable package grew from roughly 250 LoC in 2021--2022 to 6,100 LoC in 2026.

## CVE-2026-76892 - tsParticles: Malformed JSON requests can terminate the @tsparticles/mcp-server HTTP process

DevFeed: [CVE-2026-76892 - tsParticles: Malformed JSON requests can terminate the @tsparticles/mcp-server HTTP process](<https://devfeed.tech/articles/cve-2026-76892-tsparticles-malformed-json-requests-can-terminate-the-tsparticles-mcp-server-http-process-117881.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-76892>)

Author: CVEFEED.io; github.com

Published: 2026-11-04T23:17:58Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Process](<https://devfeed.tech/topics/process.md>), [JSON](<https://devfeed.tech/topics/json.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Back end](<https://devfeed.tech/topics/backend.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-76892](<https://devfeed.tech/tags/cve-2026-76892.md>), [handler](<https://devfeed.tech/tags/handler.md>), [http](<https://devfeed.tech/tags/http.md>), [json](<https://devfeed.tech/tags/json.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [process](<https://devfeed.tech/tags/process.md>), [terminate](<https://devfeed.tech/tags/terminate.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

Before version 4.3.1, the HTTP mode of @tsparticles/mcp-server parses JSON in the POST /mcp handler without a request-local error boundary. A single unauthenticated malformed JSON body can raise a SyntaxError that terminates the Node.js process, making the MCP service unavailable until an external supervisor restarts it. The issue is fixed in version 4.3.1.

### Source excerpt

CVE ID :CVE-2026-76892 Published : Nov. 4, 2026, 11:17 p.m. | 1 hour, 20 minutes ago Description :tsParticles is a TypeScript library for creating highly customizable particle animations. Prior to 4.3.1, the HTTP mode of @tsparticles/mcp-server calls JSON.parse outside a request-local error boundary in the POST /mcp handler in integrations/mcp-server/src/index.ts. A single unauthenticated malformed JSON body raises a SyntaxError that terminates the Node.js process, leaving the MCP service unavailable until an external supervisor restarts it. This issue is fixed in version 4.3.1. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## PolinRider Returns: Hijacked npm Packages Use Ethereum Blockchain to Conceal Malware Infrastructure

DevFeed: [PolinRider Returns: Hijacked npm Packages Use Ethereum Blockchain to Conceal Malware Infrastructure](<https://devfeed.tech/articles/polinrider-returns-hijacked-npm-packages-use-ethereum-blockchain-to-conceal-malware-infrastructure-119016.md>)

Original publisher: [Read original article](<https://www.ox.security/blog/polinrider-returns-hijacked-npm-packages-use-ethereum-blockchain-to-conceal-malware-infrastructure/>)

Author: Moshe Siman Tov Bustan

Published: 2026-11-04T20:59:06Z

Content type: news

Language: en

Sources: [OX Security](<https://devfeed.tech/sources/ox-security.md>)

Topics: [npm security](<https://devfeed.tech/topics/npm-security.md>), [Malware](<https://devfeed.tech/topics/malware.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [Ethereum](<https://devfeed.tech/topics/ethereum.md>), [malicious packages](<https://devfeed.tech/topics/malicious-packages.md>), [Blockchain](<https://devfeed.tech/topics/blockchain.md>), [npm](<https://devfeed.tech/topics/npm.md>), [infection chain](<https://devfeed.tech/topics/infection-chain.md>), [Cryptocurrency](<https://devfeed.tech/topics/cryptocurrency.md>)

Tags: [appsec](<https://devfeed.tech/tags/appsec.md>), [blockchain](<https://devfeed.tech/tags/blockchain.md>), [c2](<https://devfeed.tech/tags/c2.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [code](<https://devfeed.tech/tags/code.md>), [command](<https://devfeed.tech/tags/command.md>), [command-and-control](<https://devfeed.tech/tags/command-and-control.md>), [control](<https://devfeed.tech/tags/control.md>), [ethereum](<https://devfeed.tech/tags/ethereum.md>), [family](<https://devfeed.tech/tags/family.md>), [hidden](<https://devfeed.tech/tags/hidden.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [ip](<https://devfeed.tech/tags/ip.md>), [loader](<https://devfeed.tech/tags/loader.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [malware](<https://devfeed.tech/tags/malware.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-packages](<https://devfeed.tech/tags/npm-packages.md>), [overview](<https://devfeed.tech/tags/overview.md>), [ox-security](<https://devfeed.tech/tags/ox-security.md>), [packages](<https://devfeed.tech/tags/packages.md>), [polinrider](<https://devfeed.tech/tags/polinrider.md>), [research](<https://devfeed.tech/tags/research.md>)

### AI overview

OX Security reports compromised releases of legitimate npm packages linked to PolinRider. On import, an obfuscated loader queries public Ethereum RPC endpoints for a transaction containing a C2 IP, downloads an XOR-obfuscated JavaScript payload over HTTP, and executes it through an interactive Node.js process, potentially keeping activity in memory. Updating the blockchain reference can redirect affected installations without changing the published package. The affected packages total about 1,400 weekly downloads, a measure of download activity rather than confirmed infections. Recommended steps are to check dependencies and lockfiles against the affected versions, consider accessible wallets and credentials potentially compromised if the code executed, and pin dependencies to verified clean versions or apply a minimum package-age policy.

### Source excerpt

Overview OX Security researchers identified malicious releases of legitimate npm packages compromised in a campaign linked to the PolinRider malware family. The injected code uses the Ethereum blockchain as a dead drop for command-and-control (C2) infrastructure. When an affected package is imported, a hidden loader queries public Ethereum RPC endpoints to retrieve a C2 IP [...] The post PolinRider Returns: Hijacked npm Packages Use Ethereum Blockchain to Conceal Malware Infrastructure appeared first on OX Security.

## How to choose the right Cypress plugins for your project

DevFeed: [How to choose the right Cypress plugins for your project](<https://devfeed.tech/articles/how-to-choose-the-right-cypress-plugins-for-your-project-113365.md>)

Original publisher: [Read original article](<https://www.cypress.io/blog/how-to-choose-the-right-cypress-plugins-for-your-project/>)

Author: Jennifer Shehane

Published: 2026-11-02T16:41:49Z

Content type: article

Language: en

Sources: [Cypress Blog](<https://devfeed.tech/sources/cypress-blog.md>)

Topics: [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cypress](<https://devfeed.tech/tags/cypress.md>), [directory](<https://devfeed.tech/tags/directory.md>), [education](<https://devfeed.tech/tags/education.md>), [gotchas](<https://devfeed.tech/tags/gotchas.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [integrate](<https://devfeed.tech/tags/integrate.md>), [npm](<https://devfeed.tech/tags/npm.md>), [plugins](<https://devfeed.tech/tags/plugins.md>), [security](<https://devfeed.tech/tags/security.md>), [upgrades](<https://devfeed.tech/tags/upgrades.md>)

### AI overview

Choose a Cypress plugin only after checking whether Cypress or Cypress Cloud already provides the feature, its declared Cypress version range, support for your test types and browsers, data handling, and who will maintain it. Directory listings are not security reviews; scan dev dependencies, use lockfile installs in CI, and limit job secrets. Register Node code in setupNodeEvents and browser code in the relevant support file; return config so plugin changes persist. The article highlights upgrade and CI pitfalls: CYPRESS_* values populate env, while plugins using expose need options passed through --expose or copied into config.expose; CDP-based plugins work only in Chromium browsers; and support-file imports add cost to every spec. Check compatibility and migration notes before upgrades, then run the suite across your CI browsers and testing types.

### Source excerpt

Most Cypress plugins are npm packages you maintain separately from Cypress. Learn how to read the Cypress plugin directory, check a plugin against your project and security review, integrate it correctly, and fix the gotchas that show up in CI and during upgrades.

## Blocking malicious npm packages before and during installation

DevFeed: [Blocking malicious npm packages before and during installation](<https://devfeed.tech/articles/blocking-malicious-npm-packages-before-and-during-installation-112727.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/blocking-malicious-npm-packages-before-and-during-installation>)

Author: Andrew Healey

Published: 2026-11-02T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [npm security](<https://devfeed.tech/topics/npm-security.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [malicious packages](<https://devfeed.tech/topics/malicious-packages.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [npm](<https://devfeed.tech/topics/npm.md>)

Tags: [automatically](<https://devfeed.tech/tags/automatically.md>), [blocking](<https://devfeed.tech/tags/blocking.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [builds](<https://devfeed.tech/tags/builds.md>), [cache](<https://devfeed.tech/tags/cache.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [downloads](<https://devfeed.tech/tags/downloads.md>), [error](<https://devfeed.tech/tags/error.md>), [existing](<https://devfeed.tech/tags/existing.md>), [function](<https://devfeed.tech/tags/function.md>), [install](<https://devfeed.tech/tags/install.md>), [installation](<https://devfeed.tech/tags/installation.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [malware](<https://devfeed.tech/tags/malware.md>), [minutes](<https://devfeed.tech/tags/minutes.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-packages](<https://devfeed.tech/tags/npm-packages.md>), [packages](<https://devfeed.tech/tags/packages.md>)

### AI overview

Vercel checks blocked npm package versions before and during dependency installation to help prevent malicious install scripts from running. Before installation, it scans supported lockfiles, including when dependencies come from the build cache; during installation, it blocks affected public npm downloads. Existing checks of installed dependencies and function outputs continue before deployment. Protections apply automatically to new builds on all plans. When a blocked package is found, Vercel fails the deployment, names the package and version, and attempts to invalidate the affected build cache. Update the dependency and lockfile to a safe version, then redeploy.

### Source excerpt

Vercel now checks for blocked npm packages before and during dependency installation in builds, helping prevent malicious install scripts from running. The checks use a blocklist of specific package versions selected for blocking because of malware or security vulnerabilities, with new rules typically reaching new builds within minutes. Before installation, Vercel checks supported lockfiles, including when dependencies are restored from the build cache. During installation, Vercel blocks affected public npm downloads. Existing checks of installed dependencies and function outputs continue before deployment. These protections apply automatically to new builds on all plans, with no configuration required. If a blocked dependency is detected, Vercel fails the deployment, identifies the package and version in the error, and attempts to invalidate the affected build cache. Update the dependency to a safe version and update the lockfile, then redeploy. Read more

## GitHub's npm package firewall can block brand-new versions before they install

DevFeed: [GitHub's npm package firewall can block brand-new versions before they install](<https://devfeed.tech/articles/github-s-npm-package-firewall-can-block-brand-new-versions-before-they-install-105295.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/10/28/github-package-firewall-npm/>)

Author: Mirko Zorz

Published: 2026-10-28T17:09:14Z

Content type: news

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>), [npm](<https://devfeed.tech/topics/npm.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [autofix](<https://devfeed.tech/tags/autofix.md>), [build](<https://devfeed.tech/tags/build.md>), [cobol](<https://devfeed.tech/tags/cobol.md>), [code-scanning](<https://devfeed.tech/tags/code-scanning.md>), [code-security](<https://devfeed.tech/tags/code-security.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [don-t-miss](<https://devfeed.tech/tags/don-t-miss.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [github](<https://devfeed.tech/tags/github.md>), [install](<https://devfeed.tech/tags/install.md>), [malware](<https://devfeed.tech/tags/malware.md>), [news](<https://devfeed.tech/tags/news.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-package](<https://devfeed.tech/tags/npm-package.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

GitHub's npm firewall checks packages against enterprise policy before they reach a laptop, build, or coding agent. It blocks known malware, critical vulnerabilities, and brand-new versions; whether a version is new depends on package release-date metadata. Enterprises can create custom policies, including a soak or cooldown period. The three other announced additions address code scanning and remediation: AI Scan checks pull requests for vulnerabilities in languages rule-based scanning may miss, and can scan repositories on demand; a Copilot app extension surfaces code-scanning alerts, including AI Scan findings, before a pull request exists; and Autofix offers reviewable pull-request suggestions or batch Agentic Autofix across GitHub tools and more than 70 partner tools. Dependabot reachability analysis checks whether code calls a vulnerable function and exposes the call path to help teams rank alerts. This overview reflects the supplied article text.

### Source excerpt

GitHub announced a package firewall that checks npm packages against an enterprise's policy before they install. It blocks known malware, critical vulnerabilities, and brand-new versions, and any developer can turn it on by pointing npm at the firewall. The checks run before a package reaches a laptop, a build, or a coding agent. GitHub says AI agents are helping developers build more software, faster, and the firewall is one of four security additions aimed at ... More -> The post GitHub's npm package firewall can block brand-new versions before they install appeared first on Help Net Security.

## Attackers compromised 42 GitHub repositories by using files too large to be searched

DevFeed: [Attackers compromised 42 GitHub repositories by using files too large to be searched](<https://devfeed.tech/articles/attackers-compromised-42-github-repositories-by-using-files-too-large-to-be-searched-102878.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4241474/attackers-compromised-42-github-repositories-by-using-files-too-large-to-be-searched.html>)

Author: Evan Schuman

Published: 2026-10-28T02:54:12Z

Content type: news

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>), [threat detection](<https://devfeed.tech/topics/threat-detection.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [Bun](<https://devfeed.tech/topics/bun.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [actions](<https://devfeed.tech/tags/actions.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [api](<https://devfeed.tech/tags/api.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-github-security-software-development-version-control-systems-vulnerabil](<https://devfeed.tech/tags/artificial-intelligence-github-security-software-development-version-control-systems-vulnerabil.md>), [attack](<https://devfeed.tech/tags/attack.md>), [breaches](<https://devfeed.tech/tags/breaches.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [ci](<https://devfeed.tech/tags/ci.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [encrypted](<https://devfeed.tech/tags/encrypted.md>), [execution](<https://devfeed.tech/tags/execution.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [file](<https://devfeed.tech/tags/file.md>), [files](<https://devfeed.tech/tags/files.md>), [github](<https://devfeed.tech/tags/github.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [large](<https://devfeed.tech/tags/large.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>), [version-control-systems](<https://devfeed.tech/tags/version-control-systems.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

JFrog reported compromises of 42 GitHub repositories, using wrappers up to 13.7 MB that evade ordinary GitHub search and API paths and decode to a shared CI publisher payload. Hooks for Claude, Gemini, Cursor, and VS Code can trigger when a developer opens a repository; a native addon decrypts `.napi_cache` at runtime. The campaign also involved hijacked accounts, forged commit timelines, exposed npm credentials, and malicious npm releases that stole credentials and propagated through repositories and package registries. JFrog recommends treating installation of a full-worm version as host compromise, rotating exposed credentials, auditing accessible repositories for unexpected tool hooks and execution files, enumerating repository trees directly instead of relying on code search or the contents API, removing unauthorized branches and workflows, and hunting relevant runner and network indicators. The excerpt links the activity to cPanel exploitation through Shellpanel artifacts; SafeDep described the npm payload as Miasma-family but noted uncertainty about lineage.

### Source excerpt

A security research firm reported Monday that it had identified breaches of 42 third-party GitHub repositories in which attackers had deployed payload blobs large enough "to evade the GitHub search and API paths normally used to find this kind of compromise." The report from JFrog Security Research said the victimized repositories contained execution hooks for AI coding assistants and IDEs, along with polymorphic wrappers as large as 13.7MB that "all decoded to the same hidden CI-publisher payload. The campaign's attacker-owned repository also operates as an active encrypted data sink, receiving snapshot envelopes, and the attack leveraged a new camouflage: a compiled native addon that contains no payload of its own, and instead decrypts a file named .napi_cache at runtime to reveal the real one." JFrog said that the investigation also uncovered account hijacks, forged commit timelines, short-lived publishing branches and exposed npm credentials. Shellpanel artifacts in the same hijacked owner cluster link this GitHub victim infrastructure to previously reported GitHub Actions exploitation of internet-facing cPanel systems. "During October 21 our scanners alerted us about shai-hulud packages found in the npm ecosystem," JFrog wrote. "SafeDep's October 22 analysis first documented the npm/package side of this activity and decoded event-bus-lite-testmetest@0.0.1. SafeDep described the payload as Miasma-family while explicitly noting uncertainty about its lineage." SafeDep had originally thought that the packages in the campaign it had discovered, dubbed testmetest, were merely a test by the threat actor, but this week discovered the compromises of existing repos with malicious content. The JFrog post also focused on the npm chain implications. "The npm chain provides the link into the broader operation. Malicious testmetest releases used a binding.gyp command expansion to execute index.js during installation, even though the packages did not declare a conventional ins

## A Difference Without a Distinction: A Measurement Study of Release Trust Evidence in Package Registries

DevFeed: [A Difference Without a Distinction: A Measurement Study of Release Trust Evidence in Package Registries](<https://devfeed.tech/articles/a-difference-without-a-distinction-a-measurement-study-of-release-trust-evidence-in-package-registries-101350.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2606.22593>)

Author: Igor Santos-Grueiro

Published: 2026-10-27T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [pnpm](<https://devfeed.tech/topics/pnpm.md>), [trust](<https://devfeed.tech/topics/trust.md>), [project release](<https://devfeed.tech/topics/project-release.md>), [npm](<https://devfeed.tech/topics/npm.md>), [release engineering](<https://devfeed.tech/topics/release-engineering.md>), [PyPI](<https://devfeed.tech/topics/pypi.md>), [rubygems](<https://devfeed.tech/topics/rubygems.md>)

Tags: [1-6](<https://devfeed.tech/tags/1-6.md>), [2025](<https://devfeed.tech/tags/2025.md>), [account](<https://devfeed.tech/tags/account.md>), [alert](<https://devfeed.tech/tags/alert.md>), [analyze](<https://devfeed.tech/tags/analyze.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [backports](<https://devfeed.tech/tags/backports.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [branch](<https://devfeed.tech/tags/branch.md>), [central](<https://devfeed.tech/tags/central.md>), [certificates](<https://devfeed.tech/tags/certificates.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [measurement](<https://devfeed.tech/tags/measurement.md>), [package](<https://devfeed.tech/tags/package.md>), [package-registries](<https://devfeed.tech/tags/package-registries.md>), [registries](<https://devfeed.tech/tags/registries.md>), [release](<https://devfeed.tech/tags/release.md>), [study](<https://devfeed.tech/tags/study.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

The study finds that pnpm's release evidence policy blocks some legitimate updates while detecting only a limited subset of attacks. Replaying pnpm 10.29.3 across 1,997 npm packages, the authors found blocks for 1.6% of popular-package installs and 7.6% of recently updated installs, mostly due to manual backports; semver 6.3.1 accounted for 14 of 16 popular-package failures. The policy can flag an attack only when an earlier version of that package had stronger evidence. In an npm advisory census, that condition held for 17.5% of attacked packages, and attackers with observed access could have added evidence to pass 15 of 17 flagged releases. Full signing-identity pins triggered alerts for 75.8% of packages with multiple keyless-signed releases, often because certificates encode a Git branch or tag. The tested variants did not distinguish recent backports from attacks; the abstract also reports a comparison of release evidence across npm, PyPI, Maven Central, crates.io, and RubyGems but gives no comparative results.

### Source excerpt

arXiv:2606.22593v3 Announce Type: replace-cross Abstract: A stolen npm token or account lets an attacker publish a malicious version of a popular package. Such uploads skip the project's CI workflow and can lack its provenance, so since November 2025 an opt-in pnpm policy refuses any release with weaker evidence than an earlier one. Maintainers also publish backports by hand; how often the policy blocks them and which attacks it flags is unknown. We test the policy on the latest versions of 1,997 popular and recently updated npm packages, replay its variants and identity pins on reconstructed stolen-credential incidents, and analyze an npm malware advisory census. We also compare publication evidence across five package registries: npm, PyPI, Maven Central, crates.io, and RubyGems. With pnpm 10.29.3, 1.6% of popular and 7.6% of recently updated installs are blocked, mostly by backports, and one security fix backported by hand, semver 6.3.1, causes 14 of the 16 popular failures. The policy can flag an attack only if an earlier release of the same package carried stronger evidence. In the census, 17.5% of attacked packages had earlier evidence; two campaigns supply about half of these. Attackers with the observed access could have passed 15 of the 17 flagged releases by adding evidence. Pins on the full signing identity alert on 75.8% of packages with at least two keyless-signed releases, largely because certificates name the Git branch or tag. No variant tells a recent backport and an attack apart: comparing per line or declaring manual lines at the registry admits both, and an age cutoff exempts only old releases.

## How to Check and Update Your Node Version (Windows, Mac, Linux)

DevFeed: [How to Check and Update Your Node Version (Windows, Mac, Linux)](<https://devfeed.tech/articles/how-to-check-and-update-your-node-version-windows-mac-linux-101999.md>)

Original publisher: [Read original article](<https://markodenic.com/check-node-version/>)

Author: Marko

Published: 2026-10-26T20:00:00Z

Content type: tutorial

Language: en

Sources: [Marko Denic Blog](<https://devfeed.tech/sources/marko-denic-blog.md>)

Topics: [version](<https://devfeed.tech/topics/version.md>), [npm](<https://devfeed.tech/topics/npm.md>), [Homebrew](<https://devfeed.tech/topics/homebrew.md>), [Windows](<https://devfeed.tech/topics/windows.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Git](<https://devfeed.tech/topics/git.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [22](<https://devfeed.tech/tags/22.md>), [apt](<https://devfeed.tech/tags/apt.md>), [homebrew](<https://devfeed.tech/tags/homebrew.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [nvm](<https://devfeed.tech/tags/nvm.md>), [pin](<https://devfeed.tech/tags/pin.md>), [plus](<https://devfeed.tech/tags/plus.md>), [project](<https://devfeed.tech/tags/project.md>), [run](<https://devfeed.tech/tags/run.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [update](<https://devfeed.tech/tags/update.md>), [version](<https://devfeed.tech/tags/version.md>), [web-development](<https://devfeed.tech/tags/web-development.md>), [windows](<https://devfeed.tech/tags/windows.md>), [winget](<https://devfeed.tech/tags/winget.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Run `node -v` (or `node --version`) to check Node.js; use `npm -v` separately for npm. The article recommends LTS for real projects and identifies Node 24 as the safe default, with Node 26 becoming LTS on 28 October 2026. Version managers such as nvm, nvm-windows, and fnm support switching between versions and pinning a project with `.nvmrc`; nvm-windows requires removing an existing Node installation first. Alternatives include Windows `winget`, macOS Homebrew (where unversioned `node` follows the newest release, including non-LTS), and NodeSource packages for Debian and Ubuntu. Pin versions with `.nvmrc`, document supported versions in `package.json`'s `engines`, and use `actions/setup-node` to align GitHub Actions. After upgrades, npm may need a separate update, global packages may need reinstalling, and native modules may need rebuilding. The text advises checking release notes and tests before major upgrades.

### Source excerpt

Check your Node.js version with node -v, then update it with nvm, fnm, winget, Homebrew or apt. Plus which version to run in late 2026 and how to pin it per project.

## ⚡ Weekly Recap: This2Shell, That2Shell, Everything's an RCE? Rogue AI, Supply Chain Chaos and More

DevFeed: [⚡ Weekly Recap: This2Shell, That2Shell, Everything's an RCE? Rogue AI, Supply Chain Chaos and More](<https://devfeed.tech/articles/weekly-recap-this2shell-that2shell-everything-s-an-rce-rogue-ai-supply-chain-chaos-and-more-100698.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/10/weekly-recap-this2shell-that2shell.html>)

Author: The Hacker News

Published: 2026-10-26T14:06:13Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [Remote Access Trojan](<https://devfeed.tech/topics/remote-access-trojan.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Python](<https://devfeed.tech/topics/python.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [sigstore](<https://devfeed.tech/topics/sigstore.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [browser-security](<https://devfeed.tech/tags/browser-security.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [chaos](<https://devfeed.tech/tags/chaos.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [code](<https://devfeed.tech/tags/code.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [cybersecurity-recap](<https://devfeed.tech/tags/cybersecurity-recap.md>), [hackers](<https://devfeed.tech/tags/hackers.md>), [identity-security](<https://devfeed.tech/tags/identity-security.md>), [let](<https://devfeed.tech/tags/let.md>), [malware](<https://devfeed.tech/tags/malware.md>), [minutes](<https://devfeed.tech/tags/minutes.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [phishing](<https://devfeed.tech/tags/phishing.md>), [pretty](<https://devfeed.tech/tags/pretty.md>), [rce](<https://devfeed.tech/tags/rce.md>), [recap](<https://devfeed.tech/tags/recap.md>), [rogue](<https://devfeed.tech/tags/rogue.md>), [rogue-ai](<https://devfeed.tech/tags/rogue-ai.md>), [run](<https://devfeed.tech/tags/run.md>), [scanning](<https://devfeed.tech/tags/scanning.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [that-s](<https://devfeed.tech/tags/that-s.md>), [this](<https://devfeed.tech/tags/this.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [weekly](<https://devfeed.tech/tags/weekly.md>)

### AI overview

The week's clearest pattern is a surge of critical remote-code-execution flaws and rapid probing, alongside confirmed exploitation and supply-chain compromise. PHP2Shell flaws CVE-2026-109618 and CVE-2026-109619 drew millions of Cloudflare-detected attempts, but no successful exploitation had been observed; some sites went offline as a precaution. In contrast, Plex2Shell vulnerabilities were being exploited to install cryptocurrency miners and proxy software. A leaked LiteLLM master key enabled publication of a malicious package that ran at Python startup, harvested credentials, and installed a backdoor. The report also notes that the two KSMBD RCE flaws had no fixes yet and recommends restricting unprivileged user namespaces, enforcing RuntimeDefault seccomp where possible, checking for KSMBD, and patching a related privilege-escalation flaw when available. Other incidents include weak eMudhra certificate keys prompting browser blocks and the company's exit from certificate issuance, plus a compromised Downloads-folder AGENTS.md file that induced an AI coding agent to install a rogue npm package.

### Source excerpt

⚡ Weekly Recap: This2Shell, That2Shell, Everything's an RCE? Rogue AI, Supply Chain Chaos and More This2Shell, That2Shell, Everything2Shell. That's pretty much how the last week went. Critical bugs that let attackers run code remotely are showing up everywhere. Hackers are scanning for targets, som ... Read more Published Date: Oct 26, 2026 (5 hours, 38 minutes ago) Vulnerabilities has been mentioned in this article.

## How malicious downloads can trick AI coding agents into compromising themselves

DevFeed: [How malicious downloads can trick AI coding agents into compromising themselves](<https://devfeed.tech/articles/how-malicious-downloads-can-trick-ai-coding-agents-into-compromising-themselves-100448.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4240233/how-malicious-downloads-can-trick-ai-coding-agents-into-compromising-themselves.html>)

Author: Prasanth Aby Thomas

Published: 2026-10-26T10:40:38Z

Content type: news

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [prompt injection](<https://devfeed.tech/topics/prompt-injection.md>), [codex](<https://devfeed.tech/topics/codex.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>)

Tags: [agents-md](<https://devfeed.tech/tags/agents-md.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-development-tools-security-software-development](<https://devfeed.tech/tags/artificial-intelligence-development-tools-security-software-development.md>), [attack](<https://devfeed.tech/tags/attack.md>), [authentication-tokens](<https://devfeed.tech/tags/authentication-tokens.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [claude-md](<https://devfeed.tech/tags/claude-md.md>), [codex](<https://devfeed.tech/tags/codex.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [development-tools](<https://devfeed.tech/tags/development-tools.md>), [downloads](<https://devfeed.tech/tags/downloads.md>), [file](<https://devfeed.tech/tags/file.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [malware](<https://devfeed.tech/tags/malware.md>), [markdown](<https://devfeed.tech/tags/markdown.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [npm-package](<https://devfeed.tech/tags/npm-package.md>), [project](<https://devfeed.tech/tags/project.md>), [research](<https://devfeed.tech/tags/research.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>)

### AI overview

Forever Security reports that malicious Markdown instruction files can steer coding agents to install malware, alter configuration, bypass safeguards, or expose credentials by presenting harmful actions as project instructions. Codex uses AGENTS.md and Claude Code supports CLAUDE.md; the attack requires the agent to process the file in the affected directory, and Codex also requires that directory to be trusted. In tests, Codex followed the recovered instructions in more than 90% of trials, mostly with a harmless malware substitute; Claude Code configuration manipulation succeeded in about half. Researchers said Codex's machine-wide MCP change could persist across directories, while their Claude demonstration redirected API traffic and exposed tokens. A customer installation was blocked before malware ran. Researchers could not establish how the original file arrived, and an IDC expert characterized the findings as an early warning with success rates not independently validated. Suggested safeguards include human approval for security-setting changes and untrusted instruction files, reviewing instruction-file changes, keeping sandboxes enabled, limiting network access, scanning or,

### Source excerpt

Malicious instruction files planted in a computer's Downloads folder can trick AI coding agents into executing harmful code or exposing authentication tokens, Forever Security said after blocking an attempted attack on a customer's machine and demonstrating similar techniques against OpenAI's Codex and Anthropic's Claude Code. In its research report, the firm said it discovered a malicious AGENTS.md file in a customer's Downloads folder that instructed Codex to install a malicious npm package called function-color. The installation was blocked before the malware could execute. The researchers could not determine how the original file reached the computer, but demonstrated that a malicious website could trigger a similar download without a separate approval prompt. The attack exploits the way AI coding assistants process project-specific instructions. Codex uses AGENTS.md, while Claude Code supports CLAUDE.md. Both can interpret instructions contained in these Markdown files when operating in directories where the files are present. The attack requires the agent to operate in the affected directory and process the malicious file. For Codex, the directory must also be trusted, according to Forever Security. In tests using the file recovered from the customer's machine, Forever Security found that Codex could be manipulated into modifying its machine-wide MCP server configuration and launching another session with approval and sandbox restrictions bypassed. Codex followed the malicious instructions in more than 90% of tests, most of which used a harmless substitute for the malware. Because the malicious server was registered in Codex's machine-wide configuration, it could also be loaded in subsequent sessions, even after the developer moved to another directory. A separate demonstration against Claude Code showed that a malicious CLAUDE.md file could redirect the agent's API traffic to a researcher-controlled server, exposing authentication tokens and allowing the serv

## Your npm install was safe. What happens when the package runs?

DevFeed: [Your npm install was safe. What happens when the package runs?](<https://devfeed.tech/articles/your-npm-install-was-safe-what-happens-when-the-package-runs-100445.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4236783/your-npm-install-was-safe-what-happens-when-the-package-runs.html>)

Author: Sonu Kapoor

Published: 2026-10-26T09:00:00Z

Content type: opinion

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [npm](<https://devfeed.tech/topics/npm.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [branch protection rules](<https://devfeed.tech/topics/branch-protection-rules.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [out-of-process](<https://devfeed.tech/topics/out-of-process.md>)

Tags: [application](<https://devfeed.tech/tags/application.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [application-security-code-security-javascript-libraries-and-frameworks-node-js-programming-lang](<https://devfeed.tech/tags/application-security-code-security-javascript-libraries-and-frameworks-node-js-programming-lang.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [checkmarx](<https://devfeed.tech/tags/checkmarx.md>), [code](<https://devfeed.tech/tags/code.md>), [code-security](<https://devfeed.tech/tags/code-security.md>), [condition](<https://devfeed.tech/tags/condition.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [functions](<https://devfeed.tech/tags/functions.md>), [hooks](<https://devfeed.tech/tags/hooks.md>), [import](<https://devfeed.tech/tags/import.md>), [install](<https://devfeed.tech/tags/install.md>), [installation](<https://devfeed.tech/tags/installation.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [libraries-and-frameworks](<https://devfeed.tech/tags/libraries-and-frameworks.md>), [library](<https://devfeed.tech/tags/library.md>), [loader](<https://devfeed.tech/tags/loader.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [network](<https://devfeed.tech/tags/network.md>), [node](<https://devfeed.tech/tags/node.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-package](<https://devfeed.tech/tags/npm-package.md>), [package](<https://devfeed.tech/tags/package.md>), [programming-languages](<https://devfeed.tech/tags/programming-languages.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [storytype-feature](<https://devfeed.tech/tags/storytype-feature.md>)

### AI overview

Blocking npm lifecycle scripts prevents package code from running during installation, but does not establish that a dependency is safe at runtime. Checkmarx Zero reported a malicious look-alike of `sorted-btree` with no malicious install hook; its trigger was inside `BTree.prototype.set` and required a particular key condition. The excerpt recommends reviewing dependency diffs and exact resolved artifacts for new or unexpected packages, testing uncertain packages with realistic calls in an isolated environment, and limiting the secrets, filesystem, process, and network access available to processes using third-party code. These checks reduce risk but cannot prove every hidden path is safe.

### Source excerpt

For years, one of the first questions we asked about a suspicious npm package was whether it ran a pre-install or postinstall script. Those hooks can execute before a developer has written a line of code that uses the dependency. Blocking them is a sensible defense. It prevents a particular kind of package from running just because someone installed it. But installation is only the beginning of a package's life in an application. Once that application starts, it calls the package's functions with its own permissions, environment variables, network access, and data. A package can behave impeccably during installation and still become dangerous when the application uses it. That distinction is the lesson of the recently disclosed indexed-btree campaign. Checkmarx Zero found a malicious npm package that imitated the legitimate sorted-btree library. The package had no malicious install hook. Its loader sat inside BTree.prototype.set, a method the application would call as part of normal use. The reported trigger checked for a particular key value before launching an obfuscated file in a separate Node process. Merely installing the package did not trigger that behavior; neither would an import alone necessarily do so. The application had to reach the relevant method and condition. The precise key and second-stage machinery are useful to incident responders. The larger design failure is simpler: an install-time policy can tell us whether a package executed during installation. It cannot tell us whether code inside that package is safe to execute later. The wrong boundary When a team turns off life-cycle scripts, its installation process becomes safer in a specific, measurable way. npm's ignore-scripts setting prevents scripts declared in package.json from running during installation. npm also offers controls for approving install-time scripts. Neither mechanism claims to inspect every branch of a library's runtime code. We sometimes talk as though a quiet install means a

## Sign Here: Attributing a Source for a More Trustworthy Software Supply Chain

DevFeed: [Sign Here: Attributing a Source for a More Trustworthy Software Supply Chain](<https://devfeed.tech/articles/sign-here-attributing-a-source-for-a-more-trustworthy-software-supply-chain-94517.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.28794>)

Author: Derek Garcia

Published: 2026-10-22T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>), [malicious packages](<https://devfeed.tech/topics/malicious-packages.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [npm packages](<https://devfeed.tech/topics/npm-packages.md>), [PyPI](<https://devfeed.tech/topics/pypi.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [malicious-packages](<https://devfeed.tech/tags/malicious-packages.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-prevention](<https://devfeed.tech/tags/malware-prevention.md>), [npm](<https://devfeed.tech/tags/npm.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [package-registries](<https://devfeed.tech/tags/package-registries.md>), [pypi](<https://devfeed.tech/tags/pypi.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [software-supply-chain-attacks](<https://devfeed.tech/tags/software-supply-chain-attacks.md>), [source](<https://devfeed.tech/tags/source.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [transparency](<https://devfeed.tech/tags/transparency.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

The study finds that checking whether packages attribute a buildable source could prevent 87.7% to 99.9% of malware in its npm and PyPI analysis, depending on how rigorously the source is vetted. It tests building packages from source as a way to avoid the package registry attack surface, analyzing 47,066 known malicious packages and a sample of 33,138 registry packages. The approach faces a transparency constraint: only 47.4% of benign packages in the study attributed a source an end user could build from. The supplied abstract says the authors also compare this strategy with security scanners, but does not report that comparison's results.

### Source excerpt

arXiv:2610.28794v1 Announce Type: new Abstract: Software supply chain attacks continue to be on the rise, exploiting the trust that helps open source ecosystems thrive. Recent incidents like the Shai-Hulud worm and the Axios compromise demonstrate that a single malicious package can have wide reaching and devastating impacts overnight. These high profile attacks can be traced back to the same culprit: package registries. Although they are a useful convenience to pull prebuilt packages from, is such a commonly exploited component of the software supply chain worth the risk? In this paper, we investigate whether removing the registry from the developer workflow by building packages directly from source can serve as a malware prevention strategy - effectively removing an entire attack surface. Our hypothesis is that malicious packages avoid attributing a source to minimize visibility, while benign packages seek exposure and therefore link to their repositories. We evaluate this through three research questions: how effective is building from source at avoiding malware, how feasible is it to build from source in the current state of the supply chain, and how the building from source strategy compares to state-of-the-art security scanners. To do so, we (1) construct an aggregate dataset of 47,066 malicious packages from four academic and one industry malicious datasets source across npm and PyPI ecosystems, (2) build a snapshot index of all 3.9 million npm and 764 thousand PyPI packages, and (3) analyze all malicious samples alongside a statistically significant sample of 16,569 packages from each registry, totaling 33,138 packages. We find that simply checking for a source has a success rate between 87.7 and 99.9 percent of preventing malware, depending on the level of source vetting. Consequently, there is a significant lack of transparency within benign packages, with only 47.4 percent attributing a source an end user could build from.

[Next page](<https://devfeed.tech/topics/npm-packages.md?cursor=WyIyMDI2LTEwLTIyVDA0OjAwOjAwKzAwOjAwIiwgImVmYmFkNWU1LWJmYTktNDFhOC04ZjEwLWQyODgwZWFlMmY5NyJd>)