The npm package '@an1mshnpmb9c84920/pipeprobe-obf-m19n5' version 1.0.0 contains malicious code that executes during its 'prepare' lifecycle script. This script runs 'node index.js', which dynamically reconstructs a hostname and performs a DNS lookup to an external domain controlled by the attacker. This behavior confirms code execution on the installer's machine and is concealed by assembling the hostname from string fragments at runtime, evading static detection. The package offers no legitimate functionality related to this DNS callback, indicating malicious intent.
The npm package @axo_cuy/baileys version 1.0.0 declares a hard dependency on an off-registry GitHub repository (github:tenka-san/libsignal-node) without version pinning or integrity checks. This allows the third-party repository owner to change the code at any time, potentially introducing malicious code during installation. The dependency bypasses npm registry review and dependency pinning, increasing the risk of supply chain compromise.
The @bil-rgb/baileys npm package versions 1.0.0 and 1.0.1 declare a dependency on a libsignal library hosted in a personal GitHub repository without specifying a commit SHA, tag, or integrity check. This allows the dependency to resolve to the latest code at the repository's HEAD during installation, enabling arbitrary code execution controlled by the repository owner at install time. The package itself is a fork of Baileys, but the critical risk arises from the uncontrolled external dependency resolution.
The npm package 'dsh-screenshot-native' version 1.0.0 contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, uncompromised device. Removal of the package alone does not guarantee elimination of all malicious software introduced by the package.
The npm package wallet-adapter-base (version 1.0.0) is a malicious package that contains no functional code but executes a preinstall script during installation. This script sends the machine's hostname, OS username, and local time to a Discord webhook, potentially leaking sensitive environment information. The package was published by the npm user cutekitten05, who has published other packages with similar malicious scripts.
The npm package bigbob22-test@1.0.0 contains malicious code in its preinstall script that collects and sends the machine's hostname, OS username, and local time to a Discord webhook. The package itself has no functional code and an empty README. The same malicious script was used by the npm account cutekitten05 in multiple other packages published on the same date.
The 'atlassian-wallboard-plugin' npm package version 10.0.0 has been identified as malicious by the OpenSSF Package Analysis project. It is flagged because it communicates with a domain linked to malicious activity and executes commands associated with malicious behavior. There is no CVSS score or detailed impact description available.
The npm package @axon-web/icons version 99.0.0 is a malicious package that performs unauthorized data exfiltration upon loading. It constructs an identifier from the host's OS hostname and environment username, then leaks this information via DNS requests to an attacker-controlled domain. Additionally, it scans environment variables for names containing sensitive keywords related to credentials and outputs these key names, indicating reconnaissance activity. The package contains no legitimate icon content and appears to be a dependency confusion or typosquatting attack.
The hs-framework npm package declares a dependency on a tarball hosted at an external HTTPS URL rather than a versioned registry package. This tarball can be changed at any time by whoever controls the storage bucket, allowing arbitrary code execution during npm install via lifecycle scripts. The package itself is a minimal stub, with the dependency URL being the main attack surface. This setup enables supply chain compromise through dynamic, unpinned, and unverified code fetched during installation.
The npm package @goparrot-dashboard/app version 0.0.2 contains malicious code that executes automatically during installation. It collects host identifiers such as hostname, current user, and working directory, then sends this information to an attacker-controlled callback server via DNS and HTTPS requests. This data exfiltration occurs without user interaction, effectively leaking identifying information about the installer's machine.
The npm package axelarjs-sdk@1.0.1 is a malicious package that contains no functional code but executes a preinstall script during installation. This script sends the machine's hostname, OS username, and local time to a Discord webhook, potentially leaking sensitive environment information to an attacker-controlled endpoint.
The npm package 'sol-wallet-adapter' versions 1.0.0, 1.0.1, and 1.0.7 are malicious. These versions contain no functional code but execute a preinstall script that sends the machine's hostname, OS username, and local time to a Discord webhook, potentially leaking sensitive environment information. The package was published by suspicious accounts and communicates with a domain linked to malicious activity.
The npm package cutekitten-test@1.0.1 contains malicious code that executes during installation. Its preinstall script sends the machine's hostname, OS username, and local time to a Discord webhook, potentially leaking sensitive environment information. The package has no functional code beyond this data exfiltration behavior.
The npm package calculator-preinstall-hook-demo version 1.1.2 contains malicious code that executes a preinstall script during installation. This script sends the machine's hostname and OS username to a Discord webhook, potentially leaking sensitive environment information. The package was published by the npm account bigdevin55 and is pulled in as a dependency by calculator-preinstall-chain-demo@1.1.2.
The npm package calculator-preinstall-chain-demo versions 1.1.1 and 1.1.2 is identified as malicious. It does not have its own install script but depends on calculator-preinstall-hook-demo@1.1.2, which runs a preinstall script that sends the machine's hostname and OS username to a Discord webhook. This behavior is considered malicious due to unauthorized data exfiltration.
The npm package claims-ac1 version 1.0.0 is a malicious package that collects system information during installation without user consent. It uses dependencies fetched from GitHub tarballs that execute a preinstall script to send details such as Node.js version, home directory, working directory, platform, and architecture to a remote collector host. The package has no legitimate functionality and allows the attacker to change the collector host and code at any time without a new npm release. Machines with this package installed should be considered fully compromised.
The npm package @mamans2973/maman versions 1.0.0 through 1.0.3 contains malicious code that can fully compromise any computer on which it is installed or running. The compromise may allow an attacker to gain full control over the system, necessitating immediate rotation of all secrets and keys from a different, uncompromised machine. Removal of the package alone may not eliminate all malicious software introduced by it.
The ms-client-portal npm package is a malicious dependency-confusion package containing no functional code but executing scripts that send sensitive environment information to an external server during installation. It was published with versions 1.0.0 and 10.0.0 on 2026-10-31. Installation of this package results in exposure of user name, hostname, and working directory to a remote attacker. Systems with this package installed should be considered fully compromised, and all secrets and keys must be rotated immediately from a different machine.
The local-commander-agent npm package version 0.3.52 contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected machine should be rotated immediately from a different, trusted computer. Removing the package alone does not guarantee removal of all malicious software, as the attacker may have gained full control of the system.
A denial of service vulnerability exists in the joi library's string email validation when using the multiple option. The email validation splits input strings using a regular expression that performs in quadratic time on long runs of whitespace, causing the Node.js event loop to block for several seconds with large whitespace inputs. This affects joi versions from 16.0.0 through 17.13.8 and 18.0.0 through 18.3.0. The issue is fixed in joi versions 17.13.9 and 18.3.1.