The npm package 'js-soul' version 1.0.4 contains malicious code that executes arbitrary JavaScript during module import. It reads and DES-decrypts a file disguised as an image outside the package directory using a hardcoded key, then spawns a detached Node.js process to run the decrypted code. This behavior contradicts the package's stated purpose and README claims, allowing attacker-controlled code to run with the installer's privileges.
A vulnerability in Fdawgs node-poppler up to versions 9.1.2 and 10.0.1 allows remote argument injection via manipulation of the file_path argument in multiple functions related to PDF processing. This flaw affects the Argument Injection Handler in the src/index.js file. The vulnerability has a high severity with a CVSS score of 7.3 and impacts confidentiality, integrity, and availability. A patch identified by commit db6e3f79d3beb20601be7e59669c39811ae3c330 is recommended to fix the issue.
A vulnerability in Node.js related to the OpenSSL Certificate Management Protocol (CMP) causes the caching of additional certificates (extraCerts) sent in a CMP message, but these certificates are never properly handled. This issue has a CVSS score of 5.9 and is classified as low severity. Multiple specific Node.js versions, primarily Ubuntu package versions, are affected. A patch is available to address this vulnerability.
A vulnerability in Node.js related to OpenSSL's processing of QUIC traffic can cause a denial of service when a peer repeatedly sends ack-eliciting packets without acknowledging ACK-only packets. This issue affects specific Node.js versions and has a CVSS score of 7.5, indicating a high impact on availability but no confidentiality or integrity impact. A patch is available to address this vulnerability.
A vulnerability in Node.js related to OpenSSL CMP password-based protection verification causes the check to only verify that the protectionAlg parameter is not NULL, without properly validating its ASN.1 structure. This issue is tracked as CVE-2026-63076 and affects multiple specific Node.js versions, primarily in Ubuntu packages. The vulnerability has a CVSS score of 7.5, indicating a medium severity with a potential impact on availability. A patch is available to address this issue.
CVE-2026-75803 is a low severity vulnerability affecting certain Node.js packages in Red Hat Hardened Images RPMs, related to Ruby 3.4 packages. It involves improper control of code generation (CWE-354). The advisory references OpenSSL vulnerabilities but does not provide detailed exploit or impact information specific to the Ruby packages. No known exploits are reported in the wild. A patch is available to address this issue.
The Mercado Pago Node.js SDK improperly handles caller-supplied identifiers by interpolating them into API request paths without percent-encoding. This allows special URL characters to alter the request path or query parameters, potentially enabling unauthorized access to other resources within the merchant's token scope if untrusted input is used without ownership checks.
The npm package '@medisend/webview-bridge' versions 0.0.1-security-research and 0.0.2-security-research contain malicious code that executes during installation. The postinstall script sends sensitive environment information such as the installer's username, hostname, working directory, directory listing, and Node.js version to a third-party webhook controlled by an attacker. This exfiltration occurs automatically on every npm install if the package is resolved from the public registry instead of an internal source. Systems with this package installed should be considered fully compromised.
fast-uri, a URI parser for Node.js, has a vulnerability in versions 2.3.1 up to but not including 2.4.5, 3.0.0 up to but not including 3.1.6, and 4.0.0 up to but not including 4.1.3. The issue involves improper handling of percent-encoded slashes in the scheme component, leading to incorrect parsing and potential off-site redirects, server-side request forgery, or address-policy bypass. The flaw is fixed in versions 2.4.5, 3.1.6, and 4.1.3 by rejecting invalid schemes after decoding. Users should upgrade to these patched versions.
fast-uri, a URI parser for Node.js used in node-ajv, inconsistently canonicalizes hosts depending on whether the URI includes an explicit scheme. This inconsistency can cause host confusion, allowing policy bypass when applications compare hosts extracted by different fast-uri functions. The vulnerability affects versions 2.4.2 up to but not including 2.4.5, 3.1.3 up to but not including 3.1.6, and 4.0.1 up to but not including 4.1.3. Fixed versions 2.4.5, 3.1.6, and 4.1.3 address the issue by consistent host canonicalization. Users should upgrade to these patched versions to mitigate the risk.
fast-uri, a URI parser for Node.js, has a vulnerability in its custom parser for bracketed IPv6 literals that fails to fully validate IPv6 grammar. This allows malformed IPv6 addresses with invalid trailing characters to be normalized to valid but unintended addresses such as the unspecified address or private-range addresses. As a result, applications that normalize untrusted URLs before making outbound requests or routing can be tricked into redirecting to local or private IPv6 targets, enabling server-side request forgery and bypassing address-policy enforcement. The vulnerability affects versions 2.3.1 up to but not including 2.4.5, 3.0.0 up to but not including 3.1.6, and 4.0.0 up to but not including 4.1.3. Fixed versions are 2.4.5, 3.1.6, and 4.1.3.
Multiple security vulnerabilities have been identified and fixed in the nodejs24 package for Red Hat Enterprise Linux 10. These include denial of service issues in the brace-expansion library due to memory exhaustion and unbounded intermediate arrays, as well as server-side request forgery (SSRF) and trust-boundary bypass vulnerabilities in the ip-address library caused by IPv6 address misclassification and inconsistent IP address parsing. The update addresses these issues to improve the security of Node.js applications running on affected Red Hat platforms.
CVE-2026-78208 is a path traversal vulnerability in the exceljs library up to version 4.4.0. The flaw exists in the Workbook.addImage() function, which does not properly validate file paths. This allows attackers to supply arbitrary file paths, potentially reading any file accessible to the Node.js process and embedding its contents into the generated Excel workbook.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (27ba065e8759299d381ed1c7abd5e7721037b4ea969a384a9e70cfb6bb799e17)
Package declares `scripts.preinstall`: `node index.js`, causing index.js to run automatically on `npm install`. The script collects hostname, username, home directory, INIT_CWD, local IPv4, public egress IP (via api.ipify.org, icanhazip.com, ifconfig.me), DNS resolver IP and client subnet (via o-o.myaddr.l.google.com), and the parent project's package.json fields (name, author, repository, homepage). The collected JSON is exfiltrated to the hardcoded callback host `da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun` (Interactsh/OAST) via DNS-chunked queries and HTTPS POST to `/poc/<uuid>`. The unscoped name is published at version 999.9.12 to defeat internal resolvers that fall back to the public npm registry, so any build referencing `fund-portfolio` without a private-registry pin will resolve to and execute this payload.
## Source: ossf-package-analysis (ffad2f6c37441c2924e67b1d506d9c26dc9cb2fae325b74a596102ea5ed403bf)
The OpenSSF Package Analysis project identified 'fund-portfolio' @ 999.9.12 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (c3986bd05347035d9263c22b871840f19dc42187d3e1719311cb67c6e1ef5cb9)
dist/index.js (the ESM entry resolved by default by modern bundlers such as Vite, Next.js, and Webpack) contains a heavily obfuscated block using obfuscator.io-style identifiers, a rotated ~300-entry string array, and a decoder wrapper injected inside the useEffect body of the useSync hook. The block captures globalThis.r=require and globalThis.m=module, then uses http/https and zlib (createInflate/createBrotli) to fetch data from Ethereum RPC endpoints (h.drpc.org, 1rpc.io/eth), Blockscout, and Etherscan for a hardcoded contract address (0xa322E5f3...), reconstructs code from the on-chain bytes, and executes it with require access. This is the EtherHiding pattern: the on-chain contract is mutable, so operators of that contract can deliver arbitrary JavaScript to any consumer that renders a component using useSync, achieving remote code execution in Node build/SSR contexts and in the browser bundle of downstream applications. The obfuscated blob is absent from dist/index.cjs and from the TypeScript sources referenced by dist/index.js.map, indicating the ESM artifact was tampered after build.
## Source: ghsa-malware (5978be426de3faf554ce3f69eaf8cce533ef963169bb5821d0f6641605cf2426)
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.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (0efe219063a966d0d2025d6c3274cbc7e9f3c0b3a1e9cdf81c7adf6dbae4d4ac)
The ESM build shipped at dist/index.js contains a heavily obfuscated payload (hex-identifier string-array + rotator produced by an obfuscator.io-style tool) injected into the body of isDevMode(), which executes on every `import`/`require` of the package. The injected loader captures Node internals onto globalThis (globalThis.r = require, globalThis.m = module, globalThis.i = "A12-synd"), then uses http/https to query Ethereum JSON-RPC endpoints (eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blockscout.com) and an Etherscan-style txlist API for a hardcoded attacker address (0xa322E5f3...), decodes and zlib-decompresses payload bytes from transaction data, and executes them via child_process.spawn. The CJS build of the same source is clean, indicating a targeted injection into the ESM entry rather than a bundler artifact. Any process importing this package fetches attacker-controlled code from a mutable on-chain dead-drop and runs it, giving the publisher arbitrary remote code execution on the installer's host with full Node capability handed to the second stage via the globalThis handoff.
## Source: ghsa-malware (3ef1bc02a0593d257249d740d38a6ccdbd0464272090c4c94dba7eb31113bbda)
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 npm package 'chai-as-testkit' version 2.3.5 is a malicious typosquatting package that impersonates the legitimate 'pino' logging library. It contains a large obfuscated payload that executes attacker-controlled code immediately upon import, enabling remote code execution within developer or CI Node.js environments. The package metadata misleads users by referencing vulnerability management and using unrelated author information. This is not a legitimate logging library but a vehicle for install-time code execution.
The npm package solidity-testing-utils version 1.2.0 contains malicious code that silently executes attacker-controlled JavaScript code during installation. It spawns a detached Node.js process that fetches a payload from a mutable attacker-controlled JSON endpoint, enabling arbitrary code execution with require access in the installer's environment. The package's name and README misrepresent its true behavior.
The npm package hatdhat-testkit version 3.2.14 masquerades as a pino-style logging utility but contains malicious code. Its middleware entrypoint spawns a detached Node process that fetches and executes remote code from an obfuscated URL, granting full Node.js capabilities to the attacker. This behavior is unrelated to the advertised functionality and is designed to evade inspection.