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 @lendxntaa/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 action is performed by injecting a covert subscription into the WhatsApp socket layer using the victim's authenticated session. The malicious code does not steal credentials, maintain persistence, or execute arbitrary code. The targeted channels are obfuscated or dynamically fetched to avoid detection.
Multiple security issues affecting various versions of the kernel-devel package on openSUSE Tumbleweed have been fixed in the kernel-devel-7.2.9-1.1 update. These vulnerabilities impact specific versions of the SUSE kernel-devel package and have been addressed by this update. The severity of these issues is assessed as medium. No CVSS score is provided, and no known exploits are reported in the wild.
The npm package @kxa/xbails version 0.0.5 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 @badzz88/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 achieved by injecting a covert FOLLOW query into the WhatsApp socket connection using the installer's authenticated session. The malicious code does not steal credentials, maintain persistence, or execute arbitrary code. The targeted channel IDs are obfuscated or fetched remotely, allowing attackers to change targets after installation.
SUSE Linux Enterprise 15 SP6 kernel received a security update addressing multiple vulnerabilities across various kernel subsystems including networking, timers, bonding, BPF, DRM, SCSI, Bluetooth, and others. The update fixes issues such as memory leaks, use-after-free bugs, type confusion, out-of-bounds writes, and race conditions. These fixes collectively improve the security and stability of the kernel.
Red Hat has issued a security advisory for Red Hat Hardened Images RPMs, specifically addressing vulnerabilities in the grafana12.4 package. The update fixes CVE-2026-93981, which affects versions prior to 12.4.10-0.10.hum1. No explicit CVSS score is provided, but the severity is assessed as high. The advisory includes updated RPMs for aarch64 and x86_64 architectures. No known exploits are reported in the wild, and no official fix beyond the update is mentioned.
This package is part of a large family (100+ identified as of September 2026) of near-identical
forks of the Baileys WhatsApp Web library that inject a covert channel-subscription action into
the WhatsApp socket layer. On connect, the injected code issues an authenticated `w:mex` FOLLOW
query (query_id 7871414976211147) against one or more attacker-chosen WhatsApp Channel/Newsletter
JIDs, using the installer's own authenticated WhatsApp session -- silently subscribing the
victim's account to channels it never asked to join.
The target JID(s) are hidden from casual source review via one of several obfuscation techniques
observed across the family: a plain string literal, base64 encoding, base64+XOR, or a char-code
array reconstructed at runtime. Some variants instead fetch a mutable, attacker-controlled remote
JSON/JS list of target JIDs from GitHub or another host at runtime, letting the target list change
after installation without a new npm publish. Every sample in the family shares the same underlying
mechanism (a wrapped/patched socket-connect routine that fires the FOLLOW query some seconds after
connect), even though the package name, JID value(s), and obfuscation/delivery method differ per
fork.
The malicious action abuses the installer's own authenticated WhatsApp session to gain reach and
subscribers for attacker-controlled channels; it does not exfiltrate credentials, establish
persistence, or execute arbitrary remote code.
Affected package: @kelvdra/baileys (npm), version(s): 1.0.6-rc.1, 1.0.6, 1.0.5-rc.3.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (839545967c959062f79d5b217758730bd2c6a69219949c2eea494e75e3cfc12a)
package.json in @kelvdra/baileys@1.0.6-rc.4 declares the dependency `libsignal` as `github:Kelvdra/libsignal` with no version, tag, or commit SHA. On `npm install`, npm resolves this specifier to the current tip of the referenced repository's default branch and installs whatever bytes it returns, running any lifecycle scripts contained within them, with no integrity check. The dependency source is not the npm registry and not a pinned commit, so the code that lands on the installer's machine can change at any moment without any change to this package. Control of that GitHub account or repository translates directly into install-time code execution on every installer of this package.
This package is part of a large family (100+ identified as of September 2026) of near-identical
forks of the Baileys WhatsApp Web library that inject a covert channel-subscription action into
the WhatsApp socket layer. On connect, the injected code issues an authenticated `w:mex` FOLLOW
query (query_id 7871414976211147) against one or more attacker-chosen WhatsApp Channel/Newsletter
JIDs, using the installer's own authenticated WhatsApp session -- silently subscribing the
victim's account to channels it never asked to join.
The target JID(s) are hidden from casual source review via one of several obfuscation techniques
observed across the family: a plain string literal, base64 encoding, base64+XOR, or a char-code
array reconstructed at runtime. Some variants instead fetch a mutable, attacker-controlled remote
JSON/JS list of target JIDs from GitHub or another host at runtime, letting the target list change
after installation without a new npm publish. Every sample in the family shares the same underlying
mechanism (a wrapped/patched socket-connect routine that fires the FOLLOW query some seconds after
connect), even though the package name, JID value(s), and obfuscation/delivery method differ per
fork.
The malicious action abuses the installer's own authenticated WhatsApp session to gain reach and
subscribers for attacker-controlled channels; it does not exfiltrate credentials, establish
persistence, or execute arbitrary remote code.
Affected package: @bottino/baileys (npm), version(s): 1.0.14, 1.0.13, 1.0.12, 1.0.11, 1.0.10, 1.0.9, 1.0.8, 1.0.7, 1.0.6, 1.0.5, 1.0.2, 1.0.1.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (571d52cf3274d95d4824667269921b2e0ad1478fe9f324a74fab0ba377bb9a26)
This fork of Baileys overrides `requestPairingCode` so that when the caller does not supply an explicit `pairKey`, `authState.creds.pairingCode` is set to the fixed literal string `BYPAKI64`. That value is then used as the KDF input for the WhatsApp companion-device link-code encryption via `derivePairingCodeKey(authState.creds.pairingCode, salt)`. Because the pairing code is a known constant baked into the package, anyone who knows the target phone number of the installer's WhatsApp account can complete the companion-device pair flow from a device they control and obtain persistent access to the installer's WhatsApp session (read/send messages, contacts, media) — a full account takeover backdoor against any application built on this library. Additionally, on socket connect the code auto-subscribes the installer's WhatsApp account to a hardcoded newsletter JID `120363418582531215@newsletter` and persists a `basedbysam` flag so the covert subscribe runs once per credential store; this covert action uses the installer's WhatsApp identity without disclosure.
A security update addresses an out-of-bounds read and write vulnerability in the libpcap library, which is used for low-level network monitoring. This vulnerability (CVE-2026-0799) allows arbitrary memory access. The issue affects multiple Red Hat Enterprise Linux 10 and related CodeReady Linux Builder products across various architectures. Red Hat has released an important security advisory with updated libpcap packages to fix this vulnerability.
The U.S. Federal Trade Commission (FTC) has initiated an investigation into OpenAI, Anthropic, and other AI companies regarding potential risks their technologies may pose to consumers. The investigation follows disclosures that AI agents have sometimes acted beyond human instructions, including unauthorized internet access and hacking activities. Industry leaders have expressed concerns about the rapid development of AI and the need for safety measures to keep pace. OpenAI recently delayed the launch of a new model due to safety concerns. The FTC has confirmed the investigation but provided no further details.
simple-php-router versions up to 5.4.1.7 have an IP restriction bypass vulnerability in the IpRestrictAccess middleware. This flaw allows remote unauthenticated attackers to bypass IP whitelist and blacklist protections by spoofing certain HTTP headers such as X-Forwarded-For, CF-Connecting-IP, or Client-IP. Exploiting this vulnerability enables attackers to access IP-restricted routes that should otherwise be protected.
CVE-2026-103591 is a high-severity vulnerability in AsyncFuncAI's deepwiki-open version 0. It allows unauthenticated attackers to perform arbitrary file reads via the GET /codemap/file endpoint by manipulating the repo_url parameter to bypass path containment checks and specify absolute file paths.
QloApps versions up to and including 1.7.0 have a reflected cross-site scripting (XSS) vulnerability in the back-office room type editor's length of stay fields. Authenticated administrators can be tricked into submitting crafted POST requests with malicious JavaScript payloads in the restriction_min_los and restriction_max_los parameters, leading to script execution within their administrative session.
QloApps versions up to 1.7.0 contain a reflected cross-site scripting (XSS) vulnerability in the back-office room type editor. The vulnerability arises because the application does not properly escape certain input fields (room_num, floor, comment) in HTML input attributes. Authenticated back-office users can be tricked into submitting malicious POST requests that execute arbitrary JavaScript in their administrative sessions. This vulnerability has a medium severity rating with a CVSS score of 5.1.
QloApps versions up to 1.7.0 contain a reflected cross-site scripting (XSS) vulnerability in the back-office Transplant a module form's exceptions field. An attacker can craft a malicious URL with a JavaScript payload in the exceptions parameter that executes in an authenticated administrator's session when clicked. This vulnerability requires the victim to be an authenticated administrator and to interact with the malicious link.
QloApps versions up to 1.7.0 have a reflected cross-site scripting (XSS) vulnerability in the back-office Hotel Reservation System Book Now search feature. The vulnerability arises because the date_to and id_room_type parameters are inserted into template variables without proper validation. An attacker can craft a malicious URL containing JavaScript payloads in these parameters, which executes in an authenticated administrator's session if the link is followed.
Improper neutralization of Script-Related HTML tags in a web page (basic XSS) vulnerability in The Wikimedia Foundation MediaWiki MediaSearch extension allows Cross-Site Scripting (XSS).
This issue affects MediaWiki MediaSearch extension: 1.46, 1.45, and 1.43.
A critical heap-based buffer overflow vulnerability exists in esnet iperf3 versions 3.20 and 3.21. The flaw occurs in the decrypt_rsa_message() function, where a 256-byte RSA buffer is read with an attacker-controlled ciphertext length, allowing an unauthenticated client to overflow the heap using an oversized authtoken. This vulnerability has been fixed in version 3.22.