The @kanaraa/baileys npm package, a fork of the Baileys WhatsApp Web library, contains malicious code that silently subscribes the victim's WhatsApp account to attacker-controlled channels without user consent. This is done by injecting a covert channel-subscription action into the WhatsApp socket layer, issuing an authenticated FOLLOW query using the installer's WhatsApp session. The targeted channels are obfuscated or dynamically fetched, allowing attackers to modify targets after installation. The malicious code does not steal credentials, establish persistence, or execute arbitrary remote code.
The npm package @jojoxyz/condemnedforce-baileys version 2.3.0 is a malicious fork of the Baileys WhatsApp Web library. It injects code that silently subscribes the victim's WhatsApp account to attacker-controlled channels without user consent. The targeted channels are obfuscated or dynamically fetched to avoid detection. The malicious code does not steal credentials, maintain persistence, or execute arbitrary remote code.
The npm package @ikanngeming/ikannbail versions 1.0.2 through 1.0.7 is a malicious fork of the Baileys WhatsApp Web library. It injects code that silently subscribes the victim's WhatsApp account to attacker-controlled channels without user consent. This malicious behavior leverages the installer's authenticated WhatsApp session to issue covert subscription requests. The targeted channels are obfuscated or dynamically fetched. The code does not exfiltrate credentials, establish persistence, or execute arbitrary remote code.
The minecraftaccfinder package published on PyPI in multiple versions was a malicious package designed to steal credentials and session data from the victim's machine. It exfiltrated browser-stored logins and session cookies, collected the machine's public IP address and account identifiers, and sent this data to a hard-coded webhook. The package also installed persistent malware including a remote access trojan (RAT), keylogger, screenshot capture, and credential theft targeting multiple services such as Gmail, Roblox, Discord, and Minecraft. The package has been removed from PyPI.
The luoxy-baileys npm package, a fork of the Baileys WhatsApp Web library, contains malicious code that automatically subscribes the user's authenticated WhatsApp account to certain WhatsApp Channels (newsletters) chosen by the publisher. This auto-subscription occurs without explicit user consent, triggered 90 seconds after a WhatsApp connection is established. The list of channels to follow is partially hardcoded and partially fetched at runtime from a publisher-controlled GitHub URL, allowing dynamic modification of subscribed channels. The package does not exfiltrate credentials or install persistent backdoors, but it covertly inflates the publisher's channel subscriber counts. This behavior is enabled by default and undocumented except for a comparison table in the README. A user can opt out by setting a configuration flag to false.
The hridoy-ultimate npm package version 8.0.0 is an unofficial Facebook chat client containing malicious behaviors. It forwards user Facebook credentials and 2FA secrets to a hardcoded third-party server, exposing user accounts to full compromise. Additionally, it dynamically pulls and executes code from an unpinned GitHub repository during installation, allowing arbitrary code execution without integrity checks. A remote-control WebSocket client is present but opt-in and gated by configuration.
The npm package @coopeuch/core version 1.999.999 contains malicious code that executes automatically upon installation. This code collects extensive host and environment information, including system identifiers, network details, and private project metadata, and sends this data to an external server without user consent. The package uses a dependency confusion technique by adopting a high version number to override internal scoped packages. This behavior constitutes unauthorized data exfiltration during package installation.
The npm package @coopeuch/components version 1.999.999 contains malicious postinstall code that collects extensive installer environment and network metadata and exfiltrates it to a third-party server. This behavior occurs automatically during npm install and includes sensitive host, network, CI environment, and project dependency information. The package appears to be a dependency confusion attempt targeting internal @coopeuch scoped packages. No official patch or remediation guidance is provided.
The npm package @s4yhiitestpoc/scan-https-d version 1.0.0 contains malicious code that collects detailed installer host information during installation and sends it to a hardcoded external server. This includes hostname, username, home directory, current working directory, network interface addresses, DNS servers, and platform details. The package is labeled as a dependency-confusion proof-of-concept but exfiltrates sensitive environment data without user consent.
The npm package @coopeuch/common version 1.999.999 is a malicious package that uses a dependency confusion technique by publishing under a scope it does not own with an inflated version number. Upon installation, its postinstall script collects extensive host and network information from the installer's environment and exfiltrates this data to a third-party server without user consent. This includes internal hostnames, usernames, MAC addresses, internal registry URLs, and project metadata. The package README states this is a coordinated-disclosure proof of concept, but the data collection and exfiltration occur automatically and without opt-in.
The npm package @s4yhiitestpoc/r2-https version 1.0.0 contains malicious code in its postinstall script that collects detailed host environment data and sends it to a hardcoded external server without user consent. This includes sensitive information such as hostname, username, home directory, platform details, network interfaces, and npm configuration values that may reveal internal registry URLs. The script also performs an out-of-band DNS lookup to confirm execution, enabling covert data exfiltration during package installation.
The npm package @s4yhiitestpoc/r3-https version 1.0.0 contains malicious code that collects extensive host and environment information during installation. This includes host identity, network interfaces, DNS settings, and project metadata, which it sends to a hardcoded external server without user consent. This behavior is indicative of reconnaissance activity commonly associated with dependency confusion attacks.
The npm package react-paginate-v5@99.0.0 is a malicious package designed as a dependency confusion probe. It masquerades under a name similar to the legitimate react-paginate package but uses an implausibly high version number to override internal packages. Upon installation, it executes a preinstall script that performs a DNS lookup to an attacker-controlled domain, confirming the package's installation and revealing resolver metadata. The package has no legitimate functionality and can potentially execute arbitrary shell commands during installation.
The liferay-workspace-scripts npm package version 99.9.1 declares a dependency on a malicious package 'ltidisafe' hosted on a Google Cloud Storage URL. This dependency is fetched and installed without version pinning or integrity verification, allowing arbitrary code execution during npm install. The package name and version appear crafted to exploit dependency confusion, potentially executing attacker-controlled code on any machine installing this package.
The ksp-app npm package version 100.100.100 is a malicious dependency-confusion package that contains a prebuilt Linux x64 native addon. Upon installation, it executes a postinstall script that loads the native addon, which exfiltrates environment variables including HOSTNAME, npm_package_name, and npm_config_registry to a hardcoded IP address. The package exports no functional JavaScript code, indicating its sole purpose is to confirm installation in victim environments and disclose internal npm registry URLs to a third party.
The npm package ksp-client-registry versions 100.100.100 and 100.100.101 contain a malicious prebuilt native addon that, when loaded, collects environment information and sends it via a raw TCP socket to a hardcoded external IP address. This behavior occurs on package require and post-install, indicating a dependency confusion attack aimed at exfiltrating host and package details.
The npm package 'another-very-long-name' versions 1.0.1, 1.1.0, 2.0.0, and 2.0.1 contain malicious code that collects host system identifiers and sends them to a hardcoded external IP address via an unencrypted HTTP POST request. The package does not provide genuine functionality and appears to be designed for reconnaissance, likely related to dependency confusion attacks.
The npm package 'some-very-long-package-name' is a stub module that does not provide its advertised functionality. Instead, it contains malicious code that collects host and installation identifiers and sends them to a hardcoded IP address over plain HTTP. This beaconing occurs both at install time and when the module is loaded. The behavior is consistent with reconnaissance activity typical of dependency confusion or internal name squatting attacks.
The nested-lib npm package versions 1.0.0, 1.0.1, and 1.1.0 contain malicious code that sends system information to an unauthorized external server without user consent. The package executes a beacon script both during installation and when required, transmitting hostname, directory paths, and Node.js version over unencrypted HTTP to a hardcoded IP address. The package itself provides no real functionality, acting as a reconnaissance beacon likely used to confirm successful installation before further malicious activity.
The npm package pay-methods-kmf versions 100.100.100, 100.100.101, and 100.100.102 contains malicious code that exfiltrates sensitive information from the installer environment. Upon installation, it performs DNS beaconing and sends HTTP POST requests to an attacker-controlled server, leaking hostname, username, package name, and npm registry URL. The package includes a prebuilt native Linux addon with no source code, which performs these actions. This behavior is consistent with dependency confusion reconnaissance.