Checkmate is an open-source, self-hosted tool designed to track and monitor server hardware, uptime, response times, and incidents in real-time with beautiful visualizations. From 3.5.1 until 3.9.2, an authenticated admin or superadmin can set matchMethod to regex and place a malicious expression in the expectedValue field for advanced HTTP monitor matching. server/src/api/validation/monitorValidation.ts accepts the expression, and server/src/service/network/AdvancedMatcher.ts synchronously evaluates it against an attacker-controlled HTTP response body on the Node.js main event loop without a timeout or worker isolation, allowing catastrophic backtracking to freeze API endpoints, monitor checks, and WebSocket connections for all users. This issue is fixed in version 3.9.2.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (8cebaa0a3370c12104ef2816420193171f431df0d113fdc5d8c9f1dc921deeb5)
Package advertises itself as a TOTP utility but its postinstall script (`node./index.js --setup 2>/dev/null || true`) and its exported `validateSecret` API both invoke a hidden `_run()` routine that (1) scans Discord/Chrome/Edge/Brave/Opera LevelDB stores under `os.homedir()` for Discord auth-token regexes, DPAPI-decrypts encrypted tokens via a spawned powershell `ProtectedData.Unprotect` call, parses Minecraft launcher credentials (vanilla `launcher_accounts.json`, Lunar `accounts.json`, ModrinthApp `app.db` JWTs), validates the harvested Discord tokens against `discord.com/api/v9`, and POSTs the collected credentials to a hardcoded Discord webhook whose URL is stored as chunked base64 in `_x` and reassembled at runtime (`Buffer.from(_x.join(''),'base64')`) to a `discord.com/api/webhooks/1532429233769419004/...` endpoint; and (2) enumerates vanilla/Modrinth/Lunar Minecraft profile `mods/` directories and writes an opaque JAR named `optimized-renderer-1.0.0.jar` (URL also stored as chunked base64 decoding to `cdn.discordapp.com/attachments/1507484731535785994/1540335670831222894/optimized-renderer-1.0.0.jar`) into each discovered mods folder, delivering unverified code that will execute the next time the user launches Minecraft with a Fabric loader. The postinstall suppresses stderr and uses a 4-second `setTimeout` to appear to finish cleanly. Because `validateSecret` (part of the three-function public API) schedules `_run()` via `setImmediate`, the same theft and dropper also fire whenever a downstream consumer imports the package and calls the advertised TOTP function — extending the attack surface well beyond install time.
## Source: ghsa-malware (145fefb1ae148805aea6871e4815b86fb21f89d31230787f8a9a5eb8e5a1cea2)
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.
## Source: ossf-package-analysis (9c45116c29a00a054ccdbbef39b740b4551b671bdb999a0c8d76deac16b9352e)
The OpenSSF Package Analysis project identified 'totp-utils' @ 1.4.4 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
The @next-fonts/font npm package is a typosquatting malicious package impersonating Next.js's @next/font. It exports an Inter() function that decodes and executes a hidden base64 payload. This payload fetches blockchain transaction data from multiple public RPC endpoints, decrypts it, and executes arbitrary JavaScript code. This results in attacker-controlled code execution in any Node.js process that imports the package and calls Inter(), unrelated to any font functionality. The malicious behavior is obfuscated through base64 encoding, detached node process spawning, and blockchain-mediated command and control.
The mcq-session npm package versions 1.0.3 and 1.0.4 contain malicious code that executes a hidden payload. When imported, the package runs an asynchronous function that reads an external file outside the package directory, decrypts it using a hardcoded DES key, and executes the decrypted JavaScript code via a detached Node.js subprocess. This behavior bypasses static code inspection by encrypting the payload and disguising the loader with misleading identifiers. The payload file is attacker-controlled and resides alongside the host application, enabling remote code execution without user consent or verification.
The npm package express-session-handler version 2.3.3 contains malicious code that executes attacker-controlled JavaScript during module load. It performs an HTTPS fetch from a remote mutable JSON bin, extracts a field, and executes it using Function.constructor, enabling remote code execution in the Node.js process. The package disguises this behavior with unrelated code to appear legitimate.
The github-issue-bot templates in appwrite/templates verify the GitHub webhook signature with an inverted condition. verifyWebhook in node/github-issue-bot/src/github.js and in node-typescript/github-issue-bot/src/github.ts returns "typeof signature !== 'string' || (await verify(...))", so when the X-Hub-Signature-256 header is absent the first operand is true, the logical OR short-circuits, and the function reports success without performing any HMAC verification. main.js rejects a request only when verifyWebhook returns false, so an unauthenticated request carrying no signature passes the check. Processing then continues to postComment, which takes the repository and issue objects directly from the request body, letting the caller direct the deployed function to post a comment on a repository and issue of their choosing using the configured GITHUB_TOKEN, with the issue author login from the body interpolated into the comment text.
deepmerge-ts versions prior to 8.0.0 have an uncontrolled recursion vulnerability in several deep merge APIs. The merging functions do not track visited objects or pairs, causing infinite recursion when merging objects with self-references at the same property path. This leads to a synchronous crash of the Node.js process due to a maximum call stack size exceeded error. The issue is fixed in version 8.0.0.
@cgauge/yaml npm package versions up to 0.27.0 contain an arbitrary code execution vulnerability. This flaw arises from the use of a custom !js YAML tag that calls eval() on attacker-controlled strings during YAML document parsing. Applications parsing untrusted YAML with this library risk full Node.js runtime compromise, including environment, filesystem, network, and subprocess control. No safe-mode or opt-out mechanism exists to mitigate this risk within the library.
n8n versions prior to 1.123.69, 2.33.4, and 2.34.1 contain a NoSQL injection vulnerability in the MongoDB node's Find, Delete, and Aggregate operations. The vulnerability arises because the Query parameter is parsed as JSON after expression resolution without sanitizing MongoDB operators, allowing injection of special operators like $ne or $where. This can lead to unauthorized full-collection disclosure, deletion, or other database operations.
The npm package expect-dotenv version 7.2.1 contains malicious code that executes remote code from a concealed command-and-control server. When the package is required and its config() or get() functions are called, it fetches a string from a hidden URL, executes it in a Node.js VM context with full system privileges, allowing arbitrary code execution.
CVE-2026-44901 is a deserialization vulnerability in Wazuh versions from 4.0.0 up to but not including 4.14.6, and from 5.0.0-beta1 up to but not including 5.0.0-beta2. The flaw exists in the AffectedItemsWazuhResult.merge() function, which improperly trusts the sort_casting field in a cluster worker's JSON response. This allows a compromised worker to execute arbitrary Python code as root on the master node during distributed API merges. The issue is fixed in versions 4.14.6 and 5.0.0-beta2.
The npm package @wizloft/harness version 0.1.1-alpha.3 contains malicious code that performs on-chain command and control (C2) operations. Upon import, it queries a public Ethereum smart contract to retrieve a payload string, which is then executed via eval() in the Node.js process, enabling arbitrary remote code execution. The malicious payload is obfuscated and stored on-chain, making it resistant to takedown and invisible to standard registry scanners. This behavior contradicts the package README's claim of having no executable binary.
The npm package 'localize-translate' version 1.0.0 contains malicious code that executes during installation. Its postinstall script collects host identifiers such as hostname, platform, architecture, Node.js version, package name, timestamp, and npm lifecycle event, then sends this data as JSON to a hardcoded third-party server without user consent. This behavior constitutes an undisclosed, unconditional reconnaissance callback rather than legitimate telemetry.
The npm package mutex-lite version 1.4.2 is a malicious package impersonating the legitimate async-mutex library. It exports a similar Mutex API but includes hidden code that decrypts and executes an encrypted payload when triggered by a specific jobId value. This payload runs detached Node.js processes silently, potentially targeting Ethereum wallet operations via the bundled ethers library. This results in arbitrary code execution within applications that use the package and invoke the runExclusive method with the attacker-controlled jobId.
The npm package rand-txs-sdk version 1.0.3 contains malicious code hidden within its getTransactions API. This API executes a concealed payload by decoding and dynamically running obfuscated code with full Node.js privileges, including filesystem and network access. The malicious behavior is disguised through string-splicing and runtime reconstruction of critical global identifiers to evade static analysis. This loader-in-benign-wrapper attack deviates from the package's advertised functionality as a random-transaction generator.
The npm package karma-proxy version 1.0.0 contains malicious code that executes during installation. Its postinstall script collects host identifiers such as hostname, platform, architecture, Node.js version, package name, and lifecycle event, then sends this data as JSON to a hardcoded third-party endpoint unrelated to npm or the package vendor. This data collection occurs without user consent or disclosure.
The easydsbots npm package version 1.0.0 contains malicious code that executes with root privileges during installation. It uses an obfuscated install script triggered by a postinstall lifecycle hook that runs 'sudo node install.js', hiding its true behavior. The package also includes obfuscated runtime code and dependencies that enable it to register systemd or init.d services, indicating it attempts to install a persistent root-level daemon on the host system.
The npm package postcss-initialize-provider version 3.0.4 is a malicious package masquerading as a legitimate PostCSS plugin. It contains heavily obfuscated code that captures Node.js require and module objects globally, imports modules such as http, https, zlib, and child_process, and queries Ethereum blockchain RPC and block explorer endpoints to retrieve attacker-controlled payloads. These payloads are then executed via child_process.spawn, enabling remote code execution. This behavior is unexpected and malicious for a CSS transformation plugin. The package name is a typosquat of the legitimate postcss-initial project, reusing its presentation to deceive users.
The npm package localize-extract version 1.0.0 contains malicious code that executes a postinstall script. This script collects host identifiers such as hostname, platform, architecture, Node.js version, package name, and lifecycle event, then sends this data as JSON to a hardcoded external endpoint without user consent. The package appears to be a typosquatting attempt targeting the legitimate @angular/localize package, potentially as part of a dependency confusion attack.
The npm package electro-session versions 0.1.0, 0.1.1, 0.1.3, and 0.1.4 contains heavily obfuscated malicious code that acts as an infostealer. It uses Node.js built-in modules and a cloud blob upload SDK to read, decrypt, and exfiltrate local SQLite-backed credential and session stores from browsers, wallet extensions, and chat apps. The payload includes persistence mechanisms via scheduled recurring OS tasks and triggers when the package's CLI is run or when its Sessions module is instantiated.