The @coopeuch/config npm package version 1.999.999 contains malicious code that executes automatically upon installation. It collects detailed host and environment information, including host identity, network interfaces, container detection, and project metadata, then sends this data to a hardcoded external server without user consent. This behavior exposes internal infrastructure details and private project identifiers to an unauthorized third party.
The npm package nitro-bundled-dep version 99.0.1 contains malicious code that executes during installation and module import. It collects system information such as hostname, installation path, current working directory, and Node.js version, then sends this data via an unencrypted HTTP POST to a hardcoded IP address unrelated to the package's stated purpose. This behavior resembles a dependency confusion attack, where an internal package name is resolved to a malicious public package with a high version number, enabling reconnaissance on the host system.
The orderly-plugin-liquidity-heatmap npm package is a malicious supply-chain threat that activates only within GitHub Actions CI environments. It exports a non-functional stub but runs a postinstall script that collects sensitive CI runner metadata, enumerates environment variables related to GitHub Actions, captures the presence and length of the GITHUB_TOKEN, and abuses the workflow's OIDC token to access GitHub identity services. The collected data is written into the repository workspace, potentially allowing unauthorized commits and force-pushes using persisted credentials. This behavior effectively compromises the CI pipeline and can lead to full system compromise on machines where the package is installed.
The npm package 'react-dropzone-v4' version 99.0.0 is a malicious package that mimics the popular 'react-dropzone' library. It contains a preinstall script that executes automatically during installation, which performs DNS and HTTP requests to a third-party domain, transmitting the installer's hostname without consent. The package provides no legitimate functionality and appears designed for dependency confusion attacks to capture host information.
The npm package '@library-wide/library-shell' version 99.9.1 has been identified as malicious due to its communication with a domain linked to malicious activity. This behavior indicates the package may be used to facilitate harmful operations. No CVSS score is available for this threat.
The npm package 'passwordcracker' is a malicious package masquerading as a dependency-free Discord MFA library. It pulls and executes code from an attacker-controlled GitHub repository and, on Windows systems, downloads and runs a hidden script that persists through multiple startup mechanisms and checks for updates regularly. It also contains offensive functionality targeting Discord API endpoints with operator-supplied credentials and disables TLS verification for Discord domains. The package was published by the npm account 'kingsize' with identical malicious code in versions 1.0.0 and 1.1.1.
The npm package passwordcrackv2 masquerades as a dependency-free Discord MFA library but includes a malicious dependency fetched from an attacker-controlled GitHub repository. This dependency executes code on load, and on Windows systems, it downloads and runs a hidden script that persists via multiple autorun mechanisms and checks for updates regularly. The package was published by the npm account kingsize on 2026-10-09 and 2026-10-10 with identical malicious code. This behavior enables remote code execution on the installer's system regardless of the intended Discord MFA functionality.
A code injection vulnerability exists in @tinacms/cli prior to version 3.0.0 where unescaped Git branch names are directly interpolated into generated client source code. This allows an attacker controlling the branch name to inject arbitrary JavaScript expressions that execute during the consumer build process. The vulnerability arises because the branch name is inserted into a string literal without proper escaping or encoding. The impact includes arbitrary code execution with build process privileges, potentially exposing environment variables and enabling supply-chain compromise. A patch is available to fix this issue.
TinaCMS admin interface contains a critical vulnerability (CVE-2026-108261) where the preview iframe source URL is constructed from a URL fragment without proper same-origin validation. This allows an attacker to craft a URL that causes the admin to load an attacker-controlled origin in the iframe, which is then trusted by the admin's postMessage channel. Consequently, an unauthenticated remote attacker can perform arbitrary read and write GraphQL operations on the site's content API with the privileges of a logged-in editor. The vulnerability affects TinaCMS versions prior to 3.14.0 and @tinacms/app versions prior to 2.5.14. A patch is available to fix this issue by normalizing the URL and enforcing same-origin checks.
The @tinacms/web-components package's <tina-markdown> component improperly assigns link URLs directly to anchor href attributes without validating the URL scheme. This allows an attacker to craft a stored cross-site scripting (XSS) payload by using javascript: URLs in rich-text content authored in the CMS. The vulnerability affects versions prior to 0.2.1. A patch is available that adds URL scheme sanitization consistent with other sibling renderers in the repository.
The npm package @fer2809fl/baileys contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a different, trusted machine. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The cloud-baileys npm package versions 1.0.0 through 1.1.42 contain malicious code. Installing or running this package can lead to full system compromise, potentially exposing all secrets and keys stored on the affected computer. Removal of the package does not guarantee elimination of all malicious software introduced. Immediate secret and key rotation from a separate, uncompromised system is strongly advised.
The arsya-baileys npm package version 9.2.0 and related versions are malicious forks of the Baileys WhatsApp Web library. They inject code that silently subscribes the victim's WhatsApp account to attacker-controlled channels by issuing authenticated FOLLOW queries using the victim's own session. The target channels are obfuscated or dynamically fetched, allowing attackers to change targets after installation. The malicious code does not steal credentials, maintain persistence, or execute arbitrary code.
The npm package '@myorder-frontend-commons/analytics' versions 3.0.0, 10.0.0, and 99.0.0 have been identified as malicious due to communication with a domain linked to malicious activity. This behavior classifies the package as a malicious software component within the supply chain.
The npm package 'kmf-i18n' version 100.100.102 has been identified as malicious due to its communication with a domain linked to malicious activity. This behavior classifies the package as a security threat in the software supply chain.
The npm package 'test-account-portal-fe' version 100.100.102 has been identified as malicious by the OpenSSF Package Analysis project. The package is flagged because it communicates with a domain known for malicious activity. There is no CVSS score available for this threat. No official patch or remediation guidance is provided in the source data. No known exploits in the wild have been reported. The affected version is exactly 100.100.102.
The npm package 'kmf-bootstrap' versions 100.100.102 and 100.100.103 have been identified as malicious by the OpenSSF Package Analysis project. The package is flagged because it communicates with a domain linked to malicious activity. No CVSS score is available for this threat.
The npm package 'bungoma' versions 1.0.0, 1.0.1, and 1.1.0 are malicious forks of the Baileys WhatsApp Web library. These versions contain code that silently subscribes the victim's authenticated WhatsApp account to attacker-controlled channels without user consent. The target channels are obfuscated or dynamically fetched, enabling attackers to change subscription targets after installation. The malicious code abuses the installer's authenticated session but does not steal credentials, maintain persistence, or execute arbitrary code.
The npm package @bellaxchuu/teambails contains malicious code that silently subscribes a victim's authenticated WhatsApp account to attacker-controlled channels without user consent. This is done by injecting a covert subscription action into the WhatsApp socket layer, issuing an authenticated FOLLOW query to obfuscated or dynamically fetched WhatsApp Channel/Newsletter JIDs. The malicious code does not steal credentials, establish persistence, or execute arbitrary remote code.
The npm package @tunstock/remact-dom is a typosquatting malicious package impersonating the legitimate react-dom package. It includes a postinstall script that automatically runs during installation, collecting system and project information and exfiltrating it to a suspicious third-party domain. The package falsifies its identity in the data sent to the attacker’s server, indicating a reconnaissance attempt for further supply-chain compromise.