Feathersjs is a framework for creating web APIs and real-time applications with TypeScript or JavaScript. In 5.0.44 and earlier, the _.merge(target, source) utility exported by @feathersjs/commons recursively merges source into target by iterating Object.keys(source). When source was produced by JSON.parse and contains a __proto__, constructor, or prototype key, that key is returned as an own-enumerable property; the recursive merge then resolves target['__proto__'] to Object.prototype and writes attacker-supplied properties onto it, polluting the prototype for all plain objects in the process for the lifetime of the Node process. This issue is fixed in version 5.0.45.
CVE-2026-50289 is a high-severity OS command injection vulnerability in the systeminformation library for node.js. Versions prior to 5.31.7 are affected. The vulnerability arises because the networkInterfaces() function on Linux reads and parses /etc/network/interfaces, extracting a source path token that is interpolated unquoted into a shell command executed via execSync. This allows an attacker to inject arbitrary shell commands if they can control the path value. The issue is fixed in version 5.31.7.
The n8n-nodes-api-finder npm package versions 1.0.0, 1.0.1, and 1.0.2 contain malicious code that executes a reverse shell to a hardcoded command and control server. It collects host reconnaissance data and attempts Docker breakout techniques to establish persistent root SSH access on the host. The package also accesses Kubernetes configuration files and forwards them to the attacker. This malicious behavior is embedded in the package's index.js file, which runs on load, masquerading as a benign n8n community node.
The npm package 'xxdxa' contains a malicious main file that executes obfuscated code immediately upon loading. In browser contexts on the domain noviembrenacional.com, it exfiltrates the full page HTML to an attacker-controlled server and attempts to perform account takeover attacks against logged-in WordPress users by changing their account email and triggering password resets. For a specific admin user, it attempts account deletion. In Node.js environments, it leaks installation details to the attacker. The malicious behavior is heavily obfuscated to conceal attacker infrastructure and targets.
Node Version Manager (nvm) is a POSIX-compliant shell function for managing multiple node.js versions. In versions 0.32.1 through 0.40.5, `nvm ls-remote` (and other commands that refresh remote LTS aliases, such as `nvm install --lts`) parse the node.js mirror's `index.tab` and use each release's LTS codename field as an alias filename without validating it. A malicious, compromised, or man-in-the-middled mirror can return an LTS codename containing path-traversal sequences such as `../../../.bashrc`, causing nvm to write the associated version string to a path outside `$NVM_DIR/alias`. With the default layout (`$NVM_DIR` is `~/.nvm`), this can create or overwrite files in the user's home directory, including shell startup files, which can lead to code execution in a later shell session. Exploitation requires the victim to use a hostile mirror -- via a compromised mirror or CDN, a network man-in-the-middle, or a maliciously configured `NVM_NODEJS_ORG_MIRROR`/`NVM_IOJS_ORG_MIRROR` -- and to run an affected command. Version 0.40.6 validates remote LTS codenames as safe alias filenames and rejects `..` path components when writing alias files.
Cherry Studio versions 1.2.2 through 1.9.12, fixed in commit 1518530, contain a remote code execution vulnerability in SearchService that allows remote attackers to execute arbitrary code by delivering malicious JavaScript through controlled search provider content loaded into an Electron BrowserWindow configured with nodeIntegration enabled and contextIsolation disabled. Attackers who control a search engine provider, individual search result pages, or provider settings pages can execute JavaScript with full Node.js privileges, gaining access to fs, child_process, os, and process.env under the operating-system account of the Cherry Studio process.
The npm package react-hook-scripts version 5.4.2 contains malicious code that fetches and executes arbitrary JavaScript from a remote server. This remote code execution occurs via the package's default export 'getPlugin', which downloads a JSON payload from a hardcoded URL and runs the 'credits' field as code with full Node.js privileges. The malicious payload includes dependencies consistent with credential and host fingerprint stealing. Any use of the package's API triggers execution of attacker-controlled code, which can be changed at any time by the server operator.
Four AsyncAPI npm packages were compromised in July 2026, delivering Miasma v3, a new variant of the worm previously found in Red Hat packages. The malicious versions (@asyncapi/generator, @asyncapi/generator-helpers, @asyncapi/generator-components, and @asyncapi/specs) were published through AsyncAPI's legitimate GitHub Actions workflow using npm's OIDC integration, creating packages with valid provenance attestations. Unlike previous variants, this attack triggers when applications load the poisoned library rather than during installation. The payload downloads a second stage from IPFS, establishing a persistent Node.js backdoor with arbitrary shell command execution capabilities. While the codebase contains credential theft, propagation, and AI-tool poisoning modules, this deployment primarily functions as a remote access trojan. The attack began with an unauthorized commit to the repository's release branch, highlighting the importance of branch protection even when using trusted-publisher mechanisms.
Red Hat has issued an important security advisory for Node.js 24 on Red Hat Enterprise Linux 8, addressing multiple vulnerabilities in Node.js and its dependencies such as undici and ip-address. The fixes cover a range of issues including cross-site scripting, denial of service, information disclosure, authentication bypass, and man-in-the-middle attacks. The update rebases Node.js 24 to the latest upstream release, incorporating these security patches and bug fixes.
The npm package 'commonjs-assert' version 1.0.3 is a malicious package that impersonates Node.js's built-in 'assert' module. When required, it spawns a detached Node.js child process that fetches and executes remote code via an obfuscated payload, resulting in arbitrary remote code execution on the host system.
The npm package 'spytrack' is a typosquatting malicious package impersonating 'chai-spies'. When used via chai.use(), it attempts to require an undeclared package 'dbconnectify'. If this package is missing, 'spytrack' silently installs it and executes code from it without user approval or manifest review. This results in execution of externally fetched code during plugin load in the installer's Node.js process. Only version 1.1.0 of 'spytrack' is known to be affected.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (3369fb16804682addfec56904223d0255c2a0ca6d35481e744221e8252f2000d)
Package publishes as a generic 'M!T' library with an unrelated Apache-license README, but the tarball contains an offensive spam / phishing / mailbox-cracking toolkit: SMTP credential brute-force and AWS SES abuse (`func/smx/aws.js`, `func/smx/awssho.js`), IMAP/POP3/EWS/MS-OAuth mailbox checkers (`func/box/{imap,pop3,ewsv,msap,caut}.js`), phishing redirector chain (`func/rdt/*`), SOCKS/HTTP proxy rotation (`func/ipr/*`), and bulk-mailer 'zombie' senders (`func/snd/mlr/{prxml,zmbvf,zmrml}.js`). On load of the main entry `oibWljdTg.js`, `installLicenseGuard()` runs and — on integrity check — POSTs `os.hostname()`, `os.userInfo().username`, `process.cwd()`, PID, timestamp, and a bearer token read from `~/.monotomic.token` to a hardcoded author endpoint at `https://api.mntmc.rip/ibW9B3RlbmF/token/security/tamper`. `func/box/chrm.js` locates the installer's Chrome `User Data` directory (Windows `LOCALAPPDATA\Google\Chrome`, macOS `~/Library/Application Support/Google/Chrome`, Linux `~/.config/google-chrome`), launches puppeteer with `--user-data-dir=<profile>` + `--profile-directory=Default`, navigates to Outlook/Gmail URLs, and returns live session cookies (including httpOnly/secure). All 300+ source files are obfuscated with javascript-obfuscator (RC4/base64 rotated string arrays, control-flow flattening) to conceal the above behavior. `dependencies['node-ews']` is set to `github:oonlyjs/node-ews` — an unpinned mutable-branch reference under the same author account, resolved at each install, allowing arbitrary transitive code injection outside npm's tarball. Installing this package places offensive mail-abuse infrastructure on the machine, exfiltrates host identifiers and a stored bearer token to an author-controlled host on load, harvests the installer's browser session cookies, and pulls a mutable third-party dependency at install time.
## Source: ghsa-malware (d5c1f66e8c5e2e97b3fc1b3d8819b405e9187fc5fdd2cedc0882e018e2da56bd)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
The core-dotenv npm package version 1.4.1 contains malicious code that fetches and executes remote code at runtime. This behavior occurs when calling its config() or get() functions, which trigger an obfuscated HTTPS request to a remote server. The response is executed with full Node.js privileges, allowing arbitrary code execution on the host. This package should be considered fully compromised, and any system using it is at high risk.
The ogensec-sdk npm package contains a malicious Express middleware that executes arbitrary JavaScript code fetched dynamically from a configured remote server on every incoming HTTP request. This remote code execution (RCE) capability is concealed by obfuscation and undocumented as arbitrary code execution, allowing the backend maintainer or an attacker who compromises the backend to run code with full access to the Node.js process and live request/response objects. Versions 1.1.1 and 1.2.1 of the package are affected. This creates a persistent, undisclosed RCE channel in all deployments using this middleware.
The npm package polygon-toolkit-validation versions 1.0.9 and 1.1.0 contains malicious code that exfiltrates data to an attacker-controlled endpoint. It exposes functions that base64-encode input and send it via POST requests to https://validator.polymarket.shop/v2 without user consent. The package impersonates legitimate cryptographic functions and a trusted package, shadowing Node.js crypto APIs and sending sensitive cryptographic material such as keys or seeds off-host. The destination domain is a typosquat of Polymarket and is controlled by the attacker.
The npm package ai-explain version 0.3.4 contains malicious code that collects host environment information including OS username, hostname, current working directory, platform, architecture, and Node.js version. This data is sent to a hardcoded external endpoint during installation and each CLI invocation without user disclosure. The package impersonates a legitimate project to lure users. This behavior enables tracking of developer or CI machines by the attacker.
The Node.js package markdown-it, specifically its linkify-it component prior to version 5.0.1, contains an algorithmic complexity vulnerability in the LinkifyIt.prototype.match function. This function exhibits O(N²) complexity when processing inputs with many fuzzy links or emails due to repeated rescanning of progressively shorter input tails. This can lead to denial of service (DoS) conditions if untrusted Markdown with linkify enabled is synchronously rendered on a request hot path. The issue is resolved in version 5.0.1.
sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 3.2.1, the preAuthEncoding function in @sigstore/core uses Node.js ascii encoding when converting the PAE string to bytes, allowing payloadType to be mutated after signing without invalidating the signature and breaking the type-binding guarantee that DSSE is designed to provide. This issue is fixed in version 3.2.1.
The npm package 'chai-as-structured' version 7.0.5 is a malicious package designed to perform a supply-chain attack. It masquerades as a legitimate package but executes a detached Node.js child process that fetches and executes remote code with full Node privileges. The remote code is concealed using base64 encoding and is fetched from an anonymous file-hosting site. This behavior is consistent with intentional malicious activity rather than legitimate functionality.
The npm package ethereum-lib-utils@1.3.7 is a malicious impersonation of the legitimate ethereumjs-util library. It includes a deliberately injected require statement that executes code from a hidden dependency, assertion-utils-js, when imported in Node.js environments. This results in full compromise of any system with the package installed or running. Immediate removal of the package and rotation of all secrets and keys is strongly advised.