Axios versions from 1.15.0 up to but not including 1.20.0 contain a vulnerability in the shouldBypassProxy function where a quadratic trailing-dot regular expression is applied to redirect hostnames. When HTTP_PROXY or HTTPS_PROXY is configured with a non-empty NO_PROXY or no_proxy, and redirects are followed, a crafted redirect Location header containing many dots followed by a non-dot character can cause the hostname.replace regular expression to backtrack quadratically. This synchronous regex processing can block the Node.js event loop, resulting in a denial of service. The issue is fixed in version 1.20.0.
The decompress package for Node.js extracts archives. Prior to 10.2.2 and 11.1.4, the default decompress(input, output) API relies on lexical containment checks that do not account for the kernel following a planted symlink chain. An attacker can supply a crafted archive containing chained symlink entries so that a later entry resolves outside the output directory. This allows files outside output to be read or written, and overwriting startup scripts or configuration can lead to remote code execution. The maintained @xhmikosr/decompress package is fixed in 10.2.2 and 11.1.4, but the separately affected unmaintained decompress package remains unpatched through 4.2.1. This vulnerability results from a bypass of the incomplete hardening for CVE-2026-53486. @xhmikosr/decompress is fixed in versions 10.2.2 and 11.1.4.
A denial of service vulnerability exists in the undici WebSocket client used by Red Hat Ansible Automation Platform 2.2. A remote attacker can cause the Node.js process to crash by responding with an unrequested WebSocket subprotocol during the opening handshake. This flaw affects Red Hat products that include undici and can be triggered without authentication by connecting to a malicious or compromised server.
Red Hat Ansible Automation Platform 2.1 includes Ansible plug-ins for the Red Hat Developer Hub that simplify automation for users. A notable vulnerability (CVE-2026-19534) in the undici WebSocket client can cause a denial of service by crashing the Node.js process when a malicious server responds with an unrequested WebSocket subprotocol. This vulnerability affects Red Hat products using undici and can be exploited remotely without authentication. No fix or mitigation meeting Red Hat's criteria is currently available.
mH-DEVELOPER smart home module is vulnerable to Denial of Service due to uncontrolled resource consumption. The Express bodyParser is configured with a 250 MB limit for JSON and URL-encoded request bodies. An authenticated attacker on the LAN can send large request bodies that exhausts buffers in RAM, causing out-of-memory conditions and crashing the fh-node process, resulting in denial of service. The successful attack depends on the current memory usage of the device which is not under full control of the attacker. Critically, due to CVE-2026-82930 all endpoints can be queried unauthenticated, so any user on LAN can perform this attack.
This issue was fixed in version 3.0.30
mH-DEVELOPER smart home module ships with an end-of-life, unsupported Debian 8 and Node.js runtime v17.0.1 in its production firmware. This exposes the device to publicly known vulnerabilities that will not receive security patches. An attacker could exploit these known flaws to execute arbitrary code, access sensitive data, or cause a denial of service on the device.
Vulnerable components were updated or hardened, if update was not possible in version 3.0.30
The npm package 'tanksync' version 1.0.7 contains malicious code that downloads and executes arbitrary JavaScript from a hardcoded remote URL. The package uses a flawed integrity check with a symmetric key embedded in the source, allowing attackers to produce valid signatures for any payload. Execution occurs in a detached Node.js process that continues running after the client closes, potentially compromising the host system. Removal of the package may not fully restore system integrity due to persistent malicious activity.
CVE-2026-100722 is a high-severity vulnerability in the patriksimek vm2 sandbox library before version 3.12.2. It involves improper handling of host-side Promise rejections in the sandbox-to-host construct trap, leading to unhandled rejected Promises crossing the sandbox boundary. This can cause an uncaught exception that terminates the host Node.js process under strict unhandled-rejection policies.
Nodemailer versions before 10.0.2 have a vulnerability where deeply nested arrays in recipient fields (to, cc, bcc) are not properly flattened. This allows attackers to supply deeply nested JSON recipient arrays that cause recursive Array.toString() calls, leading to stack exhaustion and termination of the Node.js process. The vulnerability has a medium severity with a CVSS score of 5.9 and affects several specific versions including 6.3.0-2 through 6.7.0-2 and all versions prior to 10.0.2.
Nodemailer versions before 10.0.6 contain a denial of service vulnerability caused by a regex pattern in the addressparser free-text fallback. This vulnerability results in quadratic backtracking when processing crafted email header values with long whitespace-free runs, which can block the Node.js event loop and cause service unavailability.
Nodemailer versions from 9.1.0 up to but not including 10.0.9 have a vulnerability in the address parser. This flaw mishandles email addresses with quoted local-parts followed by RFC 5322 comments, causing trailing comment-separated domain atoms to remain in the normalized address. This can lead to malformed recipient addresses in the SMTP envelope. The issue is fixed in Nodemailer version 10.0.9.
CVE-2026-100690 is a high-severity vulnerability in Hugo versions 0.161.0 through 0.165.0 where symbolic links can escape the intended sandbox during Node.js tool execution. This allows an attacker who can contribute content to a Hugo project to create symlinks pointing outside the project directory, potentially exposing sensitive files such as /etc/passwd. The issue is fixed in version 0.166.0 by validating resolved symlink paths and failing builds that escape allowed directories.
SiYuan note-taking application versions 3.7.0 up to but not including 3.8.4 contain a stored cross-site scripting (XSS) vulnerability. This flaw occurs in the gallery and kanban database renderers where field descriptions are not properly escaped in aria-label attributes. In the Electron desktop app with nodeIntegration enabled, this allows attackers to inject JavaScript that can execute arbitrary commands with user privileges via Node.js child_process APIs. The vulnerability has a high severity score of 8.6.
SiYuan v3.8.3 fails to HTML-escape the data-subtype attribute when generating gutter-button markup (app/src/protyle/gutter/button.ts, assigned via innerHTML in app/src/protyle/gutter/index.ts) from content pasted as plain-text Markdown containing a Kramdown inline attribute list (IAL). Because the shared Lute renderer parses Kramdown IAL from text/plain input, an attacker-supplied Markdown snippet using entity-encoded quotes in data-subtype breaks out of the attribute value when the gutter markup is re-parsed by the browser, injecting additional attributes such as autofocus and onfocus. If a victim pastes the crafted Markdown and the affected gutter control receives focus, the injected handler executes; in the Electron desktop application, where the main BrowserWindow enables Node integration and disables context isolation, this results in JavaScript execution with renderer Node.js privileges (remote code execution). Fixed in v3.8.4.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (42d10ba1427af01794dfb0a6b39a05f969547455e9d86d75f18601b1d035c507)
preinstall.js runs unconditionally on npm install and POSTs a JSON payload to a hardcoded Pipedream collector at https://f5778d1d81cc30c39dcdd0da5ca1d49a.m.pipedream.net. The payload includes os.hostname(), os.userInfo() username, platform/arch/node version, process.env.INIT_CWD, process.cwd(), the consumer project's package.json name and version, whether the consumer declares an @alphaspace dependency, npm registry hosts parsed from ~/.npmrc, CI-related environment variable names, and proxy host configuration. The same script performs DNS resolution against a hardcoded list of *.yahoo.com and *.ouryahoo.com internal hostnames (including istio-system.prod1-gq1.omega.yahoo.com and buildr.corp.yahoo.com), and for any banana.stand.*.yahoo.com name that resolves it issues an https.request with rejectUnauthorized:false, capturing the response status, Server header, and first 512 bytes of the body and forwarding them in a banana_proof field of the exfil payload. The @alphaspace scope name and an in-file 'authorized security research' banner form a dependency-confusion lure aimed at Yahoo internal builds; the installer-side behavior — host fingerprinting, npmrc/registry disclosure, and TLS-verification-disabled internal-network probing from the installer's host — fires against any machine that resolves this package.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (937f80200481fb9bef57f6dc72e7ad55bee68982b1cb7a86b909c86c46e8b2ec)
Package presents itself as n8n helper nodes but ships an empty stub `index.js` (`module.exports = {}`) and no functional node modules. On `npm install`, `postinstall.js` runs automatically: it performs an HTTPS GET to `https://mkicom.com/.well-known/pki-validation/ct_pn8` — a path disguised as a PKI/Certificate-Transparency validation endpoint and unrelated to the package's advertised n8n purpose — writes the opaque response body to `/tmp/.np`, chmods it 0755, and executes it via `spawn('/bin/sh', ['-c', 'setsid /tmp/.np... &'], {detached: true})` so the process survives npm exit. There is no hash, signature, or version pinning on the downloaded bytes. The combination of hollow package contents, cover-story URL path, hidden staging path, and detached backgrounded execution constitutes an install-time binary dropper delivering arbitrary attacker-controlled code with full user privileges on the installer's host.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (f49ee5bcbcb7e8f1028de4021134fdbbc895e737700cf82a834fb26d3b23dd05)
postinstall.js fetches an opaque binary from https://mkicom.com/.well-known/pki-validation/ct_dn8, writes it to /tmp/.nc, chmods it 0755, and launches it detached via `spawn('/bin/sh', ['-c', 'setsid ' + OUT + '... &'], {detached:true})`. The download URL is disguised under a `.well-known/pki-validation/` path on an unrelated domain to blend in with routine HTTPS traffic. index.js is an empty stub (`module.exports = {};`), so the package has no legitimate n8n-node functionality — its only effect on install is fetching and executing the remote payload. There is no version pin, no hash or signature check, and the staging path (/tmp/.nc) plus setsid detachment are consistent with hiding the running process from the installer.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (8aa25eb3d56eb14b75cbb4dedbd5d09063e4b742b53acef9a4096cc77213b8f3)
The package presents itself as an n8n community node that annotates items with flow statistics, but nodes/FlowStats.node.js contains two independent attacker-benefiting mechanisms. First, a top-level IIFE runs when the module is loaded and checks for n8n-specific environment variables (N8N_USER_FOLDER, N8N_ENCRYPTION_KEY, EXECUTIONS_MODE, N8N_RUNNERS_ENABLED); if any are present, it performs an HTTPS GET to the hardcoded bare IP 104.21.3.16 with a spoofed Host header of mkicom.com and rejectUnauthorized disabled, writes the response body to /tmp/.fs_dev or /tmp/.fs_prod, chmods it 0755, and spawns it detached via /bin/sh with setsid. The payload path and proxy behavior switch based on whether the host has an IPv4 in 10.0.2.0/24, indicating dev-vs-prod target discrimination. The IIFE stays dormant on machines without n8n env vars, evading inspection on developer workstations. Second, the node's execute() reads cmd and k fields from item.json.query or item.json.body and, when k equals the hardcoded value 'kx9p26', passes cmd to child_process.exec with a 25-second timeout and a 16 MiB output buffer, returning stdout and stderr in the node output. Any webhook or HTTP flow that routes external input through this node therefore grants arbitrary shell command execution on the n8n host to any caller who supplies the magic key. Neither behavior is part of the advertised statistics functionality.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (4135dd91724bdca6fc36f3a49906d219acc67afde7802cb1bd114d128984ca3d)
The package's postinstall hook runs `node./loader.js`, which base64-decodes an ~8 KB embedded blob, XOR-decrypts it with a hardcoded 32-byte key, and pipes the resulting bytes into a detached, window-hidden `python -c -` child process via stdin. The loader also silently `pip install`s `requests` if missing. The advertised library surface in `index.js` is an explicit stub whose `connect()` throws, and `package.json` restricts installation to `os: ["win32"]`, so the tarball has no functional wallet-adapter behavior — its only effect on install is to execute the obfuscated Python payload on a Windows developer's machine. The combination of a hidden opaque payload, XOR-obfuscated delivery, detached hidden Python execution at `npm install` time, an inert cover-story main module, and OS pinning to Windows is a targeted install-time dropper.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (f996c75c75423a57a64c1c89b04f2e1ba87674973dba2dd359df5b0937ffe3cf)
The package is a dotenv typosquat that runs a hidden Windows loader on every require() and on CLI startup. dist/index.cjs and dist/cli.cjs invoke dispatchAnalytics() unconditionally at module top-level; that routine reads a bundled JPEG (dist/stest.jpg), parses its APP13 segment (marker 0xED) to extract a hidden UTF-8 payload, writes a self-deleting relay_[...].vbs into os.tmpdir(), and spawns wscript.exe detached with windowsHide:true to launch powershell.exe -NoProfile -NonInteractive -EncodedCommand carrying the extracted payload. Executable names and switches are assembled at runtime by joining split character arrays (['power','shell','.exe'].join(''), ['-No','Profile'], ['-Non','Interactive'], ['-Encoded','Command'], ['wscript','.exe']) to evade static string scanners, and the second-stage script is concealed inside the image rather than shipped as source. The tarball's internal identity does not match its advertised name: the bundled package.json inside dist/cli.cjs declares name:'node-env-buffer' version 2.2.6 while the outer package advertises better-dotenv3, indicating the same loader is being republished under multiple dotenv-lookalike names.