The cortana-md-engine npm package contains hardcoded MongoDB credentials that allow the package author to access WhatsApp session data from installed bots. This access enables potential hijacking of linked WhatsApp accounts. Additionally, the package includes offensive tools for abuse against third-party WhatsApp users, such as proxy pools and commands for flooding and banning. The malicious functionality is not disclosed in the README, misleading users about the package's true behavior.
The npm package chaienv version 1.0.2 contains a large obfuscated JavaScript payload disguised as a small Chai environment helper. The package loads a 4.4MB single-line obfuscated module that does not match the advertised functionality and includes decoy files mimicking a legitimate project to evade casual inspection. Any user importing this package executes the opaque code, which poses a risk of malicious behavior.
The npm package 'booking-eligibility' version 1.0.0 contains a malicious postinstall script that attempts to execute a Windows Script Host (WSH) VBScript file named '4444.vbs' during installation. This script is not included in the package tarball, meaning the hook either fails or could execute attacker-supplied code if the file is provided by other means. The package's README falsely claims there are no installation scripts, misleading users about its behavior. The '4444.vbs' filename suggests a potential reverse-shell payload, indicating malicious intent. The package does not provide legitimate functionality to justify this behavior.
The npm package 'developmentstelemetry' contains malicious code that executes arbitrary code during installation. Its postinstall script runs a small stub that dynamically imports and executes a function from an unaudited third-party package 'originaldevelopmentstelemetry@1.2.2', which downloads and runs an update payload on the installer's machine. This behavior effectively hands control to the external package author during every 'npm install'.
The npm package 'booking-tasks' version 1.0.2 contains a malicious postinstall script that executes a VBScript payload on Windows systems. This payload decrypts and runs a PowerShell loader via process hollowing, enabling arbitrary code execution on the host. The package's declared functionality contradicts the presence of this malicious installation script, indicating the main module acts as a decoy. The payload uses multiple cryptographic primitives and chunked Base64 encoding to evade static detection.
The test-supply-npm-lib-4 package declares a dependency via a git URL pointing to a GitHub repository controlled by an individual account rather than the official npm registry. This dependency includes lifecycle scripts, such as a prepare hook, that run automatically during npm install. Because the code is fetched directly from GitHub and not vetted through the npm registry, it poses a risk of executing malicious code on the installer's machine.
The npm package 'itsmeeaizat-bailey' includes a dependency on 'libsignal' fetched directly from a GitHub repository without version or integrity constraints, allowing the code executed during installation to change unpredictably. Additionally, the package contains an undocumented behavior that, about 90 seconds after a WhatsApp session opens, automatically issues a follow request to a hardcoded newsletter ID owned by the package author. This action uses the installer's authenticated WhatsApp identity without explicit consent. No credential theft, data exfiltration, backdoors, or destructive actions are present in the code.
The npm package tailwind-forms-kit@0.5.1 impersonates the legitimate @tailwindcss/forms plugin by using a misleading package name with a leading space, copying the README, and pointing its repository field to the legitimate source. However, its main entry point contains obfuscated code that dynamically fetches and executes arbitrary code from blockchain-hosted transaction data tied to a hardcoded Ethereum address. This allows an attacker controlling that address to execute arbitrary code on any host that installs or requires this package, bypassing typical domain or URL blocklists.
The mfahelper npm package version 1.0.0 includes a malicious dependency that fetches code from an unrelated GitHub repository's main branch without version pinning or integrity verification. This allows arbitrary code execution during installation and runtime, leading to full system compromise. Removal of the package does not guarantee elimination of the malicious payload. Immediate secret and key rotation is recommended.
The npm package web-vitals-polyfill-core-v1 version 1.0.0 is a malicious package masquerading as a legitimate web-vitals polyfill. It contains obfuscated code designed to hijack end-user navigation by loading a service worker that redirects users to attacker-controlled destinations resolved dynamically via DNS-over-HTTPS and fallback paste sites. The package lacks any legitimate library code and is intended to compromise any system where it is installed. Systems with this package installed should be considered fully compromised.
The npm package @chatunity/baileys versions 3.2.0 and 3.2.1 include a runtime dependency on libsignal from an off-registry GitHub repository without commit SHA or tag pinning. This creates a risk of arbitrary code execution during npm install if the repository content changes or if the repository owner account is compromised, due to the mutable and integrity-unchecked dependency.
A vulnerability in adm-zip version 0.6.0 allows bypassing decompression-bomb protection by setting the declared uncompressed size in a ZIP entry to zero. This causes the decompression output size limit to be ignored, potentially leading to excessive memory allocation and process crashes. The issue arises because the decompression cap is only applied when the declared size is greater than zero. A patch is available to address this flaw.
adm-zip versions prior to 0.6.1 have a vulnerability where extraction with the keepOriginalPermission=true flag preserves setuid/setgid bits from untrusted ZIP files. When extraction is performed as root, this can lead to local privilege escalation by creating root-owned setuid binaries that execute attacker-controlled code with elevated privileges.
Nodemailer versions up to 10.0.1 improperly handle deeply nested recipient arrays in fields like to, cc, and bcc. This flaw causes a stack exhaustion denial-of-service (DoS) when processing such inputs, leading to a RangeError and potential termination of the Node.js process. The vulnerability arises because only the outermost array is flattened before passing nested arrays to a parser that converts them to strings recursively, exhausting the V8 call stack. No SMTP server or successful email delivery is required to trigger this. The issue is fixed in version 10.0.2.
A vulnerability in the Joi validation library's isoDate string validation allows an attacker to cause a denial of service by sending a specially crafted string. The issue arises from a quadratic regular-expression backtracking problem that causes the validation to stall for a time proportional to the square of the input length. This can lead to significant application delays or stalls. Fixed versions are available in Joi 17.13.7 and 18.2.6.
A local race condition vulnerability exists in the Squirrel.Mac auto-update framework bundled with Electron on macOS. The privileged ShipIt helper, which runs as root to complete updates, can be tricked by a local attacker to overwrite files of a different application instead of the intended one. This affects only Electron apps on macOS that use Squirrel.Mac-based auto-updates. No workarounds exist other than updating to a patched Electron version.
Electron versions prior to 41.10.4, between 42.0.0-alpha.1 and 42.5.2, and between 43.0.0-alpha.1 and 43.0.0 allowed popups opened from sandboxed iframes with 'allow-scripts allow-popups' to drop sandbox restrictions. This enabled sandboxed content to open popups with the embedding app's full origin, potentially accessing cookies, storage, and same-origin scripting. The issue affects apps embedding untrusted content in sandboxed iframes with these permissions. Fixed versions are 41.10.4, 42.5.2, and 43.0.0.
Electron versions prior to 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5 contain a vulnerability where windows opened from a sandboxed top-level document do not inherit the document's HTML sandbox restrictions. This allows sandboxed content to open new windows with the app's full origin, potentially escalating privileges. The issue affects apps rendering untrusted content in sandboxed top-level documents that allow popups. Apps that deny popups from untrusted content using setWindowOpenHandler are not affected. Fixes are available in the specified versions.
Electron versions prior to 41.10.6, between 42.0.0-alpha.1 and 42.9.2, between 43.0.0-alpha.1 and 43.4.1, and between 44.0.0-alpha.1 and 44.0.0-beta.5 have a vulnerability where file and HTTP protocol handlers allow cross-origin reads without the corsEnabled flag. This affects apps that register custom schemes with supportFetchAPI enabled but corsEnabled disabled and load untrusted content. The vulnerability allows cross-origin reading of responses, completing a previous fix (CVE-2026-70604). Fixed versions include 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5. Setting corsEnabled to true or avoiding loading untrusted content mitigates the issue.
A vulnerability in Electron's <webview> tag allows Node.js integration to be enabled in Web Workers even when the embedder disables it, potentially granting guest content elevated privileges. This affects applications that enable the <webview> tag and run without sandboxing. The issue is fixed in Electron versions 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5. Workarounds include removing nodeIntegrationInWorker from guest preferences or avoiding <webview> usage with untrusted content.