The npm package 'kmf-vendor-pack' version 99.0.0 contains malicious code that executes automatically upon installation. It runs a postinstall script that sends an HTTPS request to an attacker-controlled domain, leaking the installer's OS hostname and username. This behavior confirms unauthorized code execution and data exfiltration without user interaction.
The pxnpm package versions 7.0.0-beta.6, 7.0.0-beta.8, 7.0.0, 7.0.1, and 7.0.2 contain malicious code that silently downloads and executes a native binary from a private host controlled by the author. During installation and every run, pxnpm forcibly replaces all user npm and proxy settings with hardcoded author-controlled registry and proxy URLs, routing all package traffic through an author-operated man-in-the-middle proxy. This allows the author to observe, log, or modify all dependency traffic without user consent or disclosure.
In late September 2026, seven malicious npm packages impersonating the NebulaAI SDK were distributed to install a Windows remote-access trojan (RAT). This RAT avoids using DLL imports by employing direct NT and win32k system calls, enabling stealthy operations such as hidden desktop remote control, kernel streaming-based camera and microphone monitoring, and persistence via the Winlogon Shell. The malware communicates with a command-and-control server at IP 65.87.7.132, disguises itself as conhost.exe, and uses anti-analysis techniques to evade detection.
The npm package @galicia-toolkit-nestjs/commons contains a malicious native binary that collects sensitive environment variables related to cloud and CI credentials, along with system information, and exfiltrates this data to a hardcoded external server. The package mimics an internal organizational scope to trick users into installing it, and it persists by daemonizing a background process. Multiple published versions are affected, and no source code or build tooling is provided for the native component, making its behavior opaque.
The npm package css-overscroll-contain versions 1.0.0 through 1.0.3 contains malicious code that executes immediately upon module load. This code performs host reconnaissance, steals credentials and sensitive environment variables, probes container escape techniques, and exfiltrates data to a hardcoded attacker endpoint. The package masquerades as a CSS utility but is incompatible with legitimate functionality. Any system with this package installed should be considered fully compromised.
A vulnerability in Borewit music-metadata versions before 11.15.0 causes an unhandled exception leading to a process crash. The issue arises from an un-awaited asynchronous call when skipping unrecognized chunks in DSF audio files, which can result in a negative argument passed to a function that throws a RangeError. This error occurs after the main parsing promise resolves, making it uncatchable by typical try/catch error handling. The impact is a denial-of-service (DoS) condition where a single crafted DSF file can crash the Node.js process using music-metadata, affecting availability.
A resource consumption vulnerability exists in Borewit's music-metadata library prior to version 11.16.0. The flaw occurs in the MP4 stsd sample-description parser where an attacker can craft an MP4 input with a zero sample-entry size and a controlled entry_count, causing an infinite synchronous loop. This leads to blocking the Node.js event loop and potentially exhausting system memory. The issue was introduced after version 11.14.0 and fixed in version 11.16.0.
A vulnerability in Borewit's music-metadata prior to version 11.16.0 allows an attacker to cause excessive memory allocation by manipulating the length of VINT elements in Matroska and WebM EBML parsers. This can lead to out-of-memory denial of service or a fatal abort in Node.js 26.7.0. The issue is fixed in version 11.16.0.
A vulnerability in Borewit's music-metadata library prior to version 11.16.0 allows excessive memory allocation due to trusting the syncsafe tag-size field in ID3v2 tags. This can cause the parser to allocate up to approximately 268 MiB of memory for a truncated file, leading to a denial of service condition. The issue is fixed in version 11.16.0.
music-metadata version 11.15.0 contains a vulnerability in its APEv2 tag parser where it allocates memory based on an untrusted size value without verifying that the declared size fits within the actual file data. This can lead to excessive memory allocation and potential denial of service. The issue is limited to availability impact and does not affect confidentiality or integrity. The vulnerability is fixed in versions after 11.15.0.
MariaDB Connector/Node.js versions prior to 3.2.5, 3.3.4, 3.4.7, and 3.5.4 contain a SQL injection vulnerability due to improper escaping of special characters in text-protocol mode when the NO_BACKSLASH_ESCAPES SQL mode is enabled. This allows an attacker to inject arbitrary SQL commands by closing string literals improperly. The vulnerability does not affect execute() and batch() methods that use binary protocols. Fixed versions have been released to address this issue.
MariaDB Connector/Node.js versions from 3.2.0 up to but not including 3.2.5, 3.3.0 up to 3.3.4, 3.4.0 up to 3.4.7, and 3.5.0-rc.0 up to 3.5.4 contain a SQL injection vulnerability when the permitSetMultiParamEntries option is enabled. This flaw allows attacker-controlled keys with backticks to inject arbitrary SQL commands, potentially modifying unintended database columns and executing commands with the database user's privileges. The option is disabled by default, and serialized-object handling when disabled is not affected. The issue is fixed in versions 3.2.5, 3.3.4, 3.4.7, and 3.5.4.
MariaDB Connector/Node.js versions prior to 3.2.5, 3.3.4, 3.4.7, and 3.5.4 contain a vulnerability where malformed GeoJSON Polygon and MultiPolygon data can cause uninitialized Node.js heap memory to be disclosed in database values. This occurs because the connector allocates buffer space based on an unchecked numeric length before verifying the ring is an array, leading to potential exposure of sensitive information such as other users' data, session material, database credentials, or TLS key material. The issue is fixed in the specified versions.
A vulnerability in mariadb-connector-nodejs versions 3.3.0 up to but not including 3.5.4 causes an uncaught exception during zero-configuration TLS authentication using the client_ed25519 plugin. This results in a denial of service where the Node.js client process crashes and exits. The issue arises because the Ed25519PasswordAuth.hash() method references an undefined variable, causing a ReferenceError. No credentials or data are exposed, but availability is impacted. The flaw can be triggered by an attacker capable of intercepting the connection and presenting a self-signed certificate. The vulnerability is fixed in version 3.5.4. Workarounds include providing the server certificate to the client or using other authentication plugins.
The npm package @kxafunc/xbails version 0.0.8 aliases its libsignal dependency to a non-standard package @bellaxchuu/libsignal-node using the mutable 'latest' dist-tag without version pinning or integrity checks. This allows whoever controls the upstream package @bellaxchuu/libsignal-node to push arbitrary code that executes within the Signal end-to-end encryption cryptographic path, potentially compromising identity keys, prekeys, and plaintext messages.
JHipster generator-jhipster versions from 7.0.0 up to but not including 9.4.0 contain an SQL injection vulnerability in reactive applications using Spring WebFlux, Spring Data R2DBC, and SQL databases. The vulnerability arises because attacker-controlled sort parameters are passed into SQL ORDER BY clauses without validation or quoting, allowing execution of additional SQL statements. This can enable an authenticated user to read sensitive data, modify or delete data, or drop tables. The issue is fixed in version 9.4.0.
CVE-2026-107303 is a cross-site scripting (XSS) vulnerability in the JHipster generator-jhipster and react-jhipster components prior to versions 9.4.0 and 1.1.0 respectively. The vulnerability allows an authenticated user with write access to store malicious Blob data that can execute active HTML or SVG content under the application origin when accessed by a privileged user. This issue arises from improper neutralization of input during web page generation and depends on the generated application's content security policy and browser Blob behavior. The vulnerability is fixed in generator-jhipster 9.4.0 and react-jhipster 1.1.0.
CVE-2026-107302 is an out-of-bounds read vulnerability in the msgpack5 library for Node.js and browsers. Versions prior to 6.1.0 improperly read the length of a map32 value before fully validating the header, causing a RangeError instead of the expected IncompleteBufferError on truncated input. This can unexpectedly terminate requests, streams, or workers that rely on the IncompleteBufferError to wait for more data. The issue does not lead to memory disclosure and is fixed in version 6.1.0.
A prototype pollution vulnerability exists in msgpack5 versions prior to 6.1.0. When constructed with an empty or partial options object, the default protection against prototype pollution is disabled. This allows a decoded map containing a __proto__ key to replace the decoded object's prototype, potentially altering inherited properties or downstream behavior. The global Object.prototype is not affected. The issue is fixed in version 6.1.0.
### Impact
The streaming decoder recursively invokes itself for every complete value remaining in a chunk. A single chunk containing many small valid MessagePack values can exhaust the JavaScript call stack and interrupt the process or stream.
### Patches
The streaming decoder now drains concatenated values iteratively with constant call-stack depth.
### Workarounds
Limit the number of MessagePack values accepted in one chunk, or split large batches before passing them to the decoder stream.