The @queenanya/baileys npm package versions 9.10.1, 9.7.3-beta.1, and 9.7.2 contain malicious code that silently subscribes the victim's WhatsApp account to attacker-controlled channels without user consent. This is achieved by injecting a covert FOLLOW query into the WhatsApp socket connection using the installer's authenticated session. The targeted channel identifiers are obfuscated or dynamically fetched, allowing attackers to change targets post-installation. The malicious code does not steal credentials, maintain persistence, or execute arbitrary code.
The @teamolduser/baileys npm package 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 subscription action into the WhatsApp socket layer, which issues an authenticated FOLLOW query using the installer's own WhatsApp session. The target channels are obfuscated or dynamically fetched, allowing attackers to change targets post-installation. The malicious code does not steal credentials, establish persistence, or execute arbitrary code.
The npm package 'anuaja' versions 1.0.0, 1.1.0, and 1.1.1 is part of a large family of malicious forks of the Baileys WhatsApp Web library. These forks inject code that silently subscribes the victim's WhatsApp account to attacker-controlled channels without user consent by issuing authenticated FOLLOW queries using the victim's own session. The target channels are obfuscated or dynamically fetched to evade detection. The malicious code does not exfiltrate credentials, establish persistence, or execute arbitrary remote code.
The eliteprotech-baileys npm package versions 1.1.0, 1.1.1, and 1.1.2 contain malicious code that silently subscribes the victim's WhatsApp account to attacker-controlled channels without user consent. This is achieved by injecting a covert subscription action into the WhatsApp socket layer, which issues an authenticated FOLLOW query using the installer's own WhatsApp session. The targeted channel IDs are obfuscated or dynamically fetched, allowing attackers to change targets post-installation. The malicious code does not exfiltrate credentials, establish persistence, or execute arbitrary remote code.
The focashi npm package version 1.1.0 is part of a large family of malicious forks of the Baileys WhatsApp Web library. These forks inject code that silently subscribes the victim's authenticated WhatsApp account to attacker-controlled channels without user consent. The malicious subscription targets are obfuscated or dynamically fetched, and the attack leverages the victim's own WhatsApp session. The code does not steal credentials, maintain persistence, or execute arbitrary remote code.
The kasabaileys npm package is a malicious fork of the Baileys WhatsApp Web library that injects code to silently subscribe the victim's WhatsApp account to attacker-controlled channels without user consent. It uses the victim's authenticated WhatsApp session to issue a covert FOLLOW query to subscribe to these channels. The target channels are obfuscated or dynamically fetched to evade detection. This behavior does not steal credentials, maintain persistence, or execute arbitrary code. Affected versions include 0.3.15, 1.0.0, 1.0.1, and 1.0.2.
The keithbaileys npm package versions 1.0.8, 1.1.0, and 1.1.1 contain malicious code that silently subscribes the victim's WhatsApp account to attacker-controlled channels without user consent. This is achieved by injecting a covert FOLLOW query into the WhatsApp socket layer using the installer's authenticated session. The target channels are obfuscated or dynamically fetched to evade detection. The malicious code does not exfiltrate credentials, establish persistence, or execute arbitrary remote code.
The npm package lilys-baileys (versions 1.3.2 and 1.3.3) is part of a large family of malicious forks of the Baileys WhatsApp Web library. These forks inject code that silently subscribes the victim's authenticated WhatsApp account to attacker-controlled channels without user consent. The malicious code uses obfuscation techniques to hide the target channel identifiers and may fetch dynamic target lists from remote hosts. The attack leverages the installer's own authenticated WhatsApp session but does not steal credentials, maintain persistence, or execute arbitrary code.
The noverojs npm package versions 1.0.1 and 1.0.4 contain malicious code that silently subscribes a victim's WhatsApp account to attacker-controlled channels without user consent. This is achieved by injecting a covert subscription action into the WhatsApp socket layer, which issues an authenticated FOLLOW query using the installer's own WhatsApp session. The target channels are obfuscated or dynamically fetched, allowing attackers to change targets post-installation. The malicious code does not exfiltrate credentials, establish persistence, or execute arbitrary remote code.
The noxxleys npm package, part of a large family of Baileys WhatsApp Web library forks, 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, which issues an authenticated FOLLOW query using the installer's own WhatsApp session. The target channels are obfuscated or dynamically fetched to evade detection. The malicious code does not steal credentials, maintain persistence, or execute arbitrary code.
The spencer-baileys npm package version 1.0.4 is a malicious fork of the Baileys WhatsApp Web library that silently subscribes the user's WhatsApp account to attacker-controlled channels without user consent. This is done by injecting code that issues an authenticated FOLLOW query using the victim's own WhatsApp session. The target channel identifiers are obfuscated or fetched remotely to evade detection. The malicious code does not steal credentials, maintain persistence, or execute arbitrary code.
The whalibmob npm package contains malicious code that silently subscribes the installer's authenticated WhatsApp account to attacker-controlled channels without user consent. This is achieved by injecting a covert channel-subscription action into the WhatsApp socket layer, issuing authenticated FOLLOW queries to attacker-chosen WhatsApp Channel/Newsletter JIDs. The targeted JIDs are obfuscated or dynamically fetched to evade detection. The malicious behavior does not exfiltrate credentials, establish persistence, or execute arbitrary remote code.
The xvinleys npm package (version 1.0.0) is a malicious fork of the Baileys WhatsApp Web library that silently subscribes the victim's WhatsApp account to attacker-controlled channels without user consent. It achieves this by injecting code that issues an authenticated FOLLOW query using the victim's own WhatsApp session. The target channels are obfuscated or dynamically fetched to evade detection. This behavior does not involve credential theft, persistence, or arbitrary code execution.
The npm package xzvbails (version 0.0.1) is a malicious fork of the Baileys WhatsApp Web library that injects code to silently subscribe the victim's WhatsApp account to attacker-controlled channels without user consent. This is done by issuing an authenticated FOLLOW query using the victim's own WhatsApp session. The targeted channel JIDs are obfuscated or fetched remotely, allowing dynamic control by the attacker. The malicious code does not steal credentials, maintain persistence, or execute arbitrary code beyond this subscription action.
The npm package yonzofficial (versions 2.1.0 through 2.1.3) is part of a large family of malicious forks of the Baileys WhatsApp Web library. These forks inject code that silently subscribes the victim's WhatsApp account to attacker-controlled channels without user consent by issuing authenticated FOLLOW queries using the victim's own WhatsApp session. The targeted channel IDs are obfuscated or dynamically fetched to evade detection. The malicious code does not steal credentials, maintain persistence, or execute arbitrary remote code.
The npm package com.epi.e2e_test version 1.2.2 contains malicious code that executes automatically during installation. A preinstall script runs an index.js file which collects host-specific identifiers such as the home directory, hostname, username, DNS servers, current working directory, and the package.json contents. This data is then sent via HTTPS to a hardcoded external server (meta.brs.cx) without user consent. This behavior is indicative of reconnaissance activity commonly associated with dependency confusion or internal name attacks.
The npm package 'reactjs-risk' versions 99.17.1 and 99.17.2 contains malicious code that executes during installation. Its preinstall script collects host identity metadata including hostname, username, and platform, encodes this data, and sends it via DNS lookup to a third-party domain without user consent. The package's main entry point is a non-functional stub, indicating the sole purpose is to exfiltrate installer information. This behavior is deliberately obfuscated to evade detection.
The npm package 'itsmeeaizat-bailey' includes a dependency on 'libsignal' fetched directly from a GitHub repository without version or integrity constraints, allowing the code executed during installation to change unpredictably. Additionally, the package contains an undocumented behavior that, about 90 seconds after a WhatsApp session opens, automatically issues a follow request to a hardcoded newsletter ID owned by the package author. This action uses the installer's authenticated WhatsApp identity without explicit consent. No credential theft, data exfiltration, backdoors, or destructive actions are present in the code.
The PyPI package 'queeuees' version 0.0.1 contains obfuscated malicious code that executes at import time. The package ships two similarly named top-level packages with identical payloads that decode and execute hidden code via complex byte transformations. This code modifies the system by iterating over Python files and adding comments without user consent. The package metadata misleads users by advertising itself as a basic calculator. The obfuscation and unauthorized system modifications indicate clear malicious intent.
WordPress patched a vulnerability called Click2Shell that allowed attackers to automatically install and preview inactive themes via specially crafted URLs. This flaw could lead to remote code execution (RCE) by abusing how theme slugs are interpreted differently by the themes API and JavaScript in an administrator's browser. Attackers could force installation of attacker-selected themes fetched from the official WordPress.org catalog without administrator consent. Some inactive third-party themes could be exploited for PHP code execution during the Customizer preview, enabling attackers to execute code under the WordPress server account without needing an attacker WordPress account. The vulnerability was fixed in WordPress version 7.1.1 and backported to versions as early as 4.7.