The npm package 'agentenact' version 0.2.0 contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted machine. Removal of the package alone may not fully eliminate the malicious presence, as the attacker may have established persistent control over the system.
A ReDoS vulnerability exists in dd-trace's URL query string obfuscation regex, causing excessive CPU usage when processing crafted inputs. This can stall request processing and lead to denial of service in applications using affected HTTP tracing integrations. The issue affects dd-trace versions >=2.0.0 <5.131.1 and >=6.0.0 <6.20.1. A fixed version is available in 5.131.1 and 6.20.1. A workaround involves setting an updated regex pattern via DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP and restarting the application.
A stored Cross-Site Scripting (XSS) vulnerability exists in the media plugin of TinyMCE. This flaw allows attackers to inject malicious scripts via elements crafted through the data-mce-object attribute, which are executed before proper sanitization. The vulnerability affects TinyMCE versions 7.9.3 and 8.5.1 up to but not including 7.9.4 and 8.9.3 respectively. It has been patched in TinyMCE 7.9.4 and 8.9.3. No official workaround is available other than upgrading.
A Cross-Site Scripting (XSS) vulnerability exists in CKEditor 5 engine versions from 29.0.0 up to but not including 47.7.4, and from 48.0.0 up to but not including 48.5.1. This issue occurs when the General HTML Support feature is enabled and configured to allow certain HTML content, enabling injection of malicious JavaScript code in a browser context isolated from the embedding application's origin. The vulnerability has a low severity score and has been patched in versions 47.7.4 and 48.5.1.
A Cross-Site Scripting (XSS) vulnerability exists in CKEditor 5 due to a prototype pollution issue in the es-toolkit library. This flaw allows unauthorized JavaScript execution when processing style attribute values. The vulnerability is fixed in CKEditor 5 versions 47.7.4 (LTS) and 48.5.1 and later.
The dsh-vm-tester npm package versions 0.1.2, 0.1.3, and 0.1.4 contain malicious code that can fully compromise any computer on which it is installed or running. This compromise includes potential unauthorized access to all secrets and keys stored on the affected system. Removal of the package alone does not guarantee elimination of all malicious components, as the attacker may have established persistent control.
undici versions 7.0.0 through before 7.30.1 and 8.0.0 through before 8.12.2 have a cache poisoning and cross-user data disclosure vulnerability when using an originless Agent with composed redirect and shared cache interceptors. The cache key is built from the original request URL before redirects change the origin, causing responses from redirected origins to be cached under the original URL. This allows an attacker controlling the redirect target to poison the cache or disclose private data to other users. The issue is fixed in versions 7.30.1 and 8.12.2 by verifying origin consistency before caching and preserving cache-control policies across redirects.
undici's Agent component improperly handles TLS options by deep cloning constructor options via JSON serialization, which drops function-valued TLS callbacks such as checkServerIdentity. This results in a TLS certificate validation bypass where custom verification logic is ignored, potentially allowing acceptance of TLS peers that should be rejected. The vulnerability affects applications using Agent as the default dispatcher for request, fetch, and setGlobalDispatcher, as well as EnvHttpProxyAgent on certain routes. Fixed in undici versions 6.29.1, 7.30.1, and 8.12.2.
undici is vulnerable to a denial of service condition triggered by a TLS 1.2 server-initiated renegotiation presenting a different, valid but hostname-mismatched certificate. This causes an uncaught assertion error that crashes the Node.js client process, affecting both HTTP/1.1 and HTTP/2. Only TLS 1.2 is impacted, as TLS 1.3 does not support renegotiation. The issue is fixed in undici versions 6.29.1, 7.30.1, and 8.12.2. Mitigation includes upgrading to these versions or restricting connections to TLS 1.3 to prevent renegotiation.
undici's WebSocket client, including Node.js's bundled globalThis.WebSocket, is vulnerable to a denial of service condition caused by unbounded automatic PONG buffering. A malicious WebSocket server can send continuous PING frames causing the client to queue PONG responses without respecting backpressure, leading to memory exhaustion and process termination. This affects undici versions from 5.15.0 up to but not including 6.29.1, 7.0.0 up to 7.30.1, and 8.0.0 up to 8.12.2. Upgrading to versions 6.29.1, 7.30.1, or 8.12.2 mitigates the issue by properly handling backpressure.
A vulnerability in undici's decompress interceptor allows a denial of service via an unhandled exception. When the decompress interceptor forwards decompressed data to a downstream handler that throws an exception asynchronously (such as the dump interceptor with a maxSize limit), the exception is uncaught and terminates the Node.js process. This can be triggered by a malicious HTTP server sending a small compressed response that decompresses to a size exceeding the limit. The issue affects undici versions >=7.15.0 <7.30.1 and >=8.0.0 <8.12.2. Fixed in versions 7.30.1 and 8.12.2.
Certain versions of the MCP TypeScript SDK and related packages do not limit HTTP POST request body size or JSON-RPC batch length. This allows an attacker to send very large requests or long batches, potentially exhausting server memory and causing denial of service. No authentication is required unless implemented outside the SDK. Fixed versions impose limits on request size and batch length.
@webapp-shared/login-vmok is a malicious npm package designed for dependency confusion attacks. It impersonates an internal scoped package and was published with multiple versions containing a postinstall script that sends sensitive host information to a remote server over unencrypted HTTP. The package also sends this data whenever it is loaded, disclosing internal hostnames and filesystem paths to an attacker-controlled endpoint. Placeholder versions without malicious code exist but are not affected.
The adyen-web-v6 npm package contains malicious code that compromises any computer on which it is installed or running. Systems with this package should be considered fully compromised, necessitating immediate rotation of all secrets and keys from a separate, secure machine. Removal of the package alone may not eliminate all malicious software introduced by it.
The npm package 'buttoncontent' contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, clean machine. Removing the package alone may not fully remove the malicious software or restore system integrity.
The qs library version 6.7.0 through 6.16.0 has a vulnerability in its stringify function when using the arrayFormat 'comma'. If an array element has a non-callable own toString property, qs.stringify throws an uncaught TypeError. This can be triggered remotely by an unauthenticated attacker controlling input that is later serialized with this option, potentially crashing the Node.js process and causing a denial of service. There is no impact on confidentiality or integrity, and no prototype pollution occurs.
The undici WebSocket client, when using HTTP/2 (enabled by default with allowH2: true), crashes the Node.js process if it connects to a malicious server that responds with a failed WebSocket handshake over HTTP/2. This occurs because the client aborts the request too late, leaving an open HTTP/2 stream that emits an unhandled error when the server closes the connection, causing a denial of service. Versions 8.11.0 and 8.11.1 are affected. A fix is available in version 8.11.2. Workarounds include disabling HTTP/2 for WebSocket connections or avoiding untrusted servers until patched.
The npm package 'string-target-mapper-hash' contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted machine. Removal of the package alone does not guarantee elimination of all malicious software, as the attacker may have gained full control of the system.
The npm package 'macro-kernel-record-reader' is identified as containing malicious code. Any system with this package installed or running is considered fully compromised, potentially allowing an attacker full control over the computer. Immediate rotation of all secrets and keys stored on the affected system is recommended, using a different, uncompromised machine. Removal of the package is advised, but it may not fully eliminate the malicious presence due to possible persistent backdoors or additional malware installed.
The npm package 'fetch-hash-cache-atomic' contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a separate, trusted machine. Removal of the package alone is insufficient to guarantee the elimination of all malicious software introduced by this package.