The magika-js npm package is a typosquat of Google's legitimate magika library. It contains a postinstall script that collects various host identifiers such as hostname, platform, architecture, Node.js version, package name, npm lifecycle event, and timestamp. This data is sent as JSON to a hardcoded external endpoint without user consent or documented purpose. The package impersonates the legitimate Google project by referencing its GitHub repository. This behavior constitutes malicious code embedded in the package.
The npm package 'gaarf-node-bq' version 1.0.0 is a malicious typosquatting package targeting the internal 'gaarf' package used by Google Ads API report fetcher. It contains a postinstall script that collects host metadata such as hostname, platform, architecture, Node.js version, package name, and npm lifecycle event, then sends this data without user consent to a hardcoded external endpoint. The package itself provides no legitimate functionality and acts as a canary for dependency confusion attacks.
The npm package gaarf-bq 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, and package metadata, then sends this data to a hardcoded external server without user consent. This behavior is unrelated to the package's documented functionality and resembles dependency confusion tactics. No official patch or remediation guidance is provided.
The npm package config-helper-kit version 1.3.2 contains malicious code that executes attacker-controlled JavaScript. It does this by fetching code from a hardcoded IP address and running it within the Node.js process of any consumer that imports and invokes the default export. This behavior is undocumented and unrelated to the package's advertised purpose as a TypeScript/Tailwind config helper. This allows arbitrary code execution on the host running the package.
The npm package 'chrome-enterprise-premium-mcp' version 1.0.0 contains a postinstall script that automatically executes upon installation. This script collects metadata about the installer environment, including hostname, platform, architecture, Node version, package name, npm lifecycle event, and timestamp. It then sends this information as JSON to a hardcoded external URL controlled by an unauthorized third party. The package name mimics a legitimate Google Chrome Enterprise product, indicating a typosquatting or dependency confusion attempt to identify and track users who install it.
The npm package 'broadcast-graphics-mcp' version 1.0.0 contains malicious code in its postinstall script that automatically executes upon installation. This script collects host identifiers such as hostname, platform, architecture, Node.js version, package name, npm lifecycle event, and timestamp, then sends this data as JSON to a hardcoded external server controlled by the package author. This behavior results in the exfiltration of installer machine metadata without user consent or configuration options.
The streak-key-lib npm package version 1.0.0 contains malicious code disguised as a dependency-free, browser-safe day-math helper. Despite claiming no network or filesystem interaction, it includes a large obfuscated block that executes on import, using an RC4/XOR decoder and self-defense techniques to evade analysis. The package is designed as a supply-chain stager, executing hidden code at import time and misleading consumers by promoting companion packages instead of direct installation. This behavior poses a risk of unauthorized code execution in Node.js environments that import this package.
The npm package sui-gql-rpc version 1.0.1 contains malicious code that executes arbitrary JavaScript on the installer's machine if the installer's git identity matches targeted developer profiles. This code decrypts attacker-controlled payloads using a key derived from the installer's git config email and username, then executes the decrypted code with the installer's Node.js privileges. The malicious payload is designed to avoid execution in CI environments and sandboxes by checking environment variables and silently swallowing errors. The package name impersonates the Sui GraphQL RPC namespace to deceive developers in that ecosystem.
The timed-assess npm package versions 1.0.0 and 1.0.1 contain malicious code that executes attacker-controlled JavaScript during installation. The postinstall script decrypts a bundled payload using a hardcoded DES key and runs it in a detached Node.js process, suppressing output to avoid detection.
The npm package sw-pluginer masquerades as a Tailwind plugin but contains malicious code that executes arbitrary JavaScript fetched from a URL specified in a transient manifest.json file. This file is staged in node_modules/.bin and deleted after reading, concealing the payload source. The fetched code is executed via eval() in the Node.js build environment without any integrity checks, enabling remote code execution on the developer's machine during build time.
The tfjs-custom-module npm package is a typosquatting malicious package impersonating the tensorflow/tfjs package. It contains a postinstall script that automatically runs on installation and collects host system identifiers such as hostname, platform, architecture, Node.js version, package name, and npm lifecycle event. This data is exfiltrated via an HTTPS POST request to a hardcoded external domain controlled by the attacker. This behavior constitutes unauthorized host reconnaissance and data exfiltration without user consent.
The npm package txs-lib-sdk version 1.0.2 contains malicious code that executes arbitrary Node.js commands on the host system. Its getTransactions() API reads a disguised file, decodes and deobfuscates a payload, then executes it with full system privileges. This behavior is hidden through multiple layers of obfuscation and is not legitimate for the package's stated purpose. Any system with this package installed should be considered fully compromised.
The ts-rand-sdk npm package contains malicious code that executes a hidden payload with full Node.js capabilities on the host machine. It disguises itself as a random transactions SDK but loads and executes obfuscated JavaScript code from a disguised data file. This code execution grants arbitrary filesystem, process, and network access, effectively compromising any system running the package. Immediate removal and secret/key rotation are strongly advised.
The npm package 'tfjs-inference' version 1.0.0 is a typosquatting package targeting TensorFlow.js. It contains a postinstall script that automatically collects host identifiers such as hostname, platform, architecture, Node.js version, and package name, then sends this data as JSON to a hardcoded third-party server without user consent or notification. The package internally labels itself as a security research canary, but the data exfiltration destination is controlled by the author, raising significant privacy and security concerns.
The npm package tailwind-utility-kit version 1.3.2 contains malicious code that executes arbitrary attacker-controlled code on any host that loads it. The package assembles a concealed URL pointing to a remote IP address, fetches JSON data, and executes the 'credits' field as code with full Node.js privileges. This behavior enables full compromise of the host environment. The package also includes decoy metadata to disguise its malicious intent and dependencies consistent with credential-stealing payloads.
The tailwind-extension-kit npm package version 1.3.2 contains malicious code that executes attacker-controlled JavaScript on the developer's machine. Its default export fetches JSON from a hardcoded IP address and executes the data using a dynamic function constructor with full Node.js privileges. The package masquerades as a Tailwind CSS utility but includes code consistent with credential and cookie stealing. This malicious behavior is triggered when the package is registered as a Tailwind plugin, leading to remote code execution.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (7695ac02a2492bbf3118fc68514378edb201a93183f2dcb0035727781f31d408)
fast-glob-fast is a name-squat of the popular fast-glob package (its repository field even points at mrmlnc/fast-glob). The declared postinstall hook `node scripts/postinstall-test.mjs` computes the installer's `~/.ssh/authorized_keys` path per-platform (darwin/linux/win32), creates `~/.ssh` at mode 0700 if missing, and appends to `authorized_keys` at mode 0600 via `appendFileSync`. The same script defines a top-level constant `DEFAULT_TEXT = 'ssh-ed25519 AAAAC3NzaC1lZDI1NTE5... dkhrustalev'` — a staged attacker ed25519 public key. Appending any key line to authorized_keys grants passwordless SSH login as the installing user; even though the current build only appends comment lines, the primitive, the target file, and the embedded attacker key together form a persistence/remote-access dropper wired to run automatically on `npm install`. The same postinstall additionally collects `username`, `hostname`, non-internal MAC address, `platform`, and `arch`, and POSTs them as a JSON `systemInfo` event (optionally with a bearer token) to a URL taken from `FAST_GLOB_FAST_EVENT_URL`, reporting the outcome of the authorized_keys write — a reporting channel co-located with the backdoor primitive.
Adaguc-server is an open source geographical information system to visualize, combine, compare and share real-time meteorological, climatological and remote sensing data via OGC standards. Versions prior to 7.2.2 crash with a memory-safety fault when it parses a GeoJSON document whose geometry contains a malformed coordinate. The coordinate parser in `adagucserverEC/CConvertGeoJSON.cpp` indexes `pt.u.array.values[0]` and `pt.u.array.values[1]` and uses `polygon.u.array.length` as a loop bound without first validating the JSON node type or the coordinate length. A coordinate that is an empty array, a one-element array, a scalar, or `null` leads to an out-of-bounds heap read or a NULL pointer dereference. The same unchecked pattern is present in four geometry branches: `Polygon`, `LineString`, `MultiLineString` and `MultiPolygon`. The vulnerable parser runs whenever the server processes a local GeoJSON file, either a configured GeoJSON dataset or a GeoJSON file exposed through the `AutoResource` feature and requested by an unauthenticated WMS request. A crafted GeoJSON file reliably crashes the backend process that handles that request. Version 7.2.2 patches the vulnerability.
A critical vulnerability (CVE-2026-75926) in Hugo versions 0.162.0 through 0.164.x allows arbitrary command execution due to insecure default permissions when running TailwindCSS. The vulnerability arises because TailwindCSS is launched with --allow-child-process permission, enabling code in tailwind.config.js to spawn shell processes with full user privileges. This breaks the intended Node.js permission confinement introduced in Hugo 0.161.0. The issue is fixed in Hugo 0.165.0 by removing TailwindCSS from the default allowed child process list.
CodeWhale versions before 0.8.64 contain an environment variable exposure vulnerability in the js_execution tool that fails to scrub parent process environment variables before spawning Node.js. Attackers can craft malicious JavaScript code executed by the tool to read process.env and leak API keys, cloud credentials, and authentication tokens back to the model context.