The npm package 'nodemon-copack' impersonates the legitimate 'nodemon' project by copying its source code and metadata, including homepage, author, and repository fields. It introduces two runtime dependencies, 'regex-js' and 'chai', which are not used in the package code but are pulled into the installer's dependency graph. This pattern suggests dependency smuggling, where the actual malicious payload may reside in these transitive dependencies. Although the package itself does not contain direct malicious actions such as exfiltration or remote code execution, the presence of these smuggled dependencies poses a risk. The package versions 3.1.15 and 3.1.16 are affected. The package should be considered malicious, and any system with it installed should be treated as compromised.
The npm package weavedb-contracts version 0.45.2 was compromised as part of the IronWorm campaign. The malicious code executes a Rust-based infostealer during installation via a preinstall hook, targeting developer credentials for cloud providers, databases, source control, package registries, AI tools, and cryptocurrency wallets. It also injects malicious JavaScript into the Exodus wallet to capture sensitive data. The malware exhibits worm-like behavior by stealing GitHub and npm credentials to propagate itself through repositories and trojanized packages. Additionally, it uses an eBPF-based kernel rootkit on Linux to hide its presence. Installing this package can lead to full system compromise.
The hbsig npm package versions 0.3.1 and 0.3.2 were compromised as part of the IronWorm campaign. The malicious package executes a Rust-based infostealer during installation that targets developer credentials for cloud services, databases, source control, package registries, AI tools, and cryptocurrency wallets. It injects malicious code into the Exodus wallet to capture sensitive data and uses worm-like behavior to spread by stealing GitHub and NPM credentials to push malicious updates. Additionally, it employs an eBPF-based kernel rootkit on Linux to hide its presence. Systems with this package installed should be considered fully compromised and require immediate secret rotation from a clean environment.
The Danelec MacGregor Voyage Data Recorder (VDR) G4e contains a vulnerability due to the presence of a default username and password that is not enforced to be changed by users. This weakness allows unauthorized access to the device, potentially compromising confidentiality, integrity, and availability of the data recorded. The vulnerability has a high severity with a CVSS score of 8.3. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.
Incorrect behavior order in the Infotainment / Digital Round display of the Indian Motorcycle Scout Bobber + Tech 2025 model year allows an adjacent-network attacker to bypass the PIN entry screen. The Infotainment uses presence of Wireless Control Module (WCM) traffic during its boot window as a proxy for whether an immobilizer is fitted; if no WCM messages are observed, it skips the PIN entry screen and shows the normal user interface. An attacker who silences the WCM during the boot window — for example via a separately tracked CAN bus-off technique — can present a fully unlocked Infotainment despite the PIN never being entered. Specific timing and protocol details have been withheld pending vendor remediation.
Incorrect behavior order in the Infotainment / Digital Round display of the Indian Motorcycle Scout Bobber + Tech 2025 model year allows an adjacent-network attacker to bypass the PIN entry screen. The Infotainment uses presence of Wireless Control Module (WCM) traffic during its boot window as a proxy for whether an immobilizer is fitted; if no WCM messages are observed, it skips the PIN entry screen and shows the normal user interface. An attacker who silences the WCM during the boot window — for example via a separately tracked CAN bus-off technique — can present a fully unlocked Infotainment despite the PIN never being entered. Specific timing and protocol details have been withheld pending vendor remediation.
CVE-2026-47272 is a high-severity vulnerability in pam_usb versions prior to 0.9.0 that allows improper authentication. The flaw exists because the authentication function pusb_pad_compare() only verified the presence and readability of the user-side pad file (~/. pamusb/device.pad) but did not enforce verification of the system-side pad file on the USB device. If the user-side pad file is deleted or unreadable, the function returns a failure treated as non-fatal in some code paths, enabling a local user to bypass the USB device requirement and authenticate without the physical device. This vulnerability is fixed in version 0.9.0.
A vulnerability in the Linux kernel's netfilter arp_tables component causes incorrect parsing of IEEE1394 (FireWire) ARP payloads. The arp_packet_match() function incorrectly assumes the presence of a target hardware address, which is omitted in IPv4-over-IEEE1394 ARP, leading to misinterpretation of packet data and incorrect filtering decisions. This can cause packets to be wrongly accepted or dropped. Additionally, attempts to mangle certain ARP fields on IEEE1394 devices can corrupt packets due to miscalculated offsets. The issue has been fixed by adjusting the parsing logic and dropping packets when unsafe mangling is requested on IEEE1394 devices.
The weavedb-client npm package version 0.45.3 contains a malicious preinstall script that executes a UPX-packed Linux ELF binary during installation. This binary acts as an infostealer targeting developer credentials such as SSH/PuTTY private keys, GitHub tokens, OAuth/Discord tokens, and environment variables. It also injects malicious code into the Exodus cryptocurrency wallet to capture sensitive data and uses worm-like behavior to propagate by stealing GitHub and npm credentials. The malware employs an eBPF-based kernel rootkit on Linux to hide its presence. Installation of this package version can lead to full system compromise.
The weavedb-offchain npm package version 0.45.4 was compromised by the IronWorm campaign, which introduced a malicious preinstall hook executing a large ELF binary. This binary acts as an infostealer targeting developer credentials, cloud secrets, cryptocurrency wallets, and uses advanced techniques including eBPF kernel rootkits to hide its presence. The malware can propagate by stealing GitHub and npm credentials to push malicious updates and trojanized packages. Any system installing this package version is considered fully compromised.
The npm package 'cwao-units' version 0.8.3 contains a malicious preinstall script that executes a large opaque native Linux binary. This binary acts as an infostealer targeting developer credentials, cloud secrets, cryptocurrency wallets, and uses kernel rootkit techniques to hide its presence. It also exhibits worm-like behavior by stealing GitHub and npm credentials to propagate further malicious packages. The package is part of the IronWorm campaign and fully compromises any system where it is installed.
The weavedb-base npm package version 0.45.3 contains a malicious preinstall script that executes a packed Linux ELF binary during installation. This binary acts as an infostealer targeting developer credentials, cryptocurrency wallets, and uses kernel rootkit techniques to hide its presence. The malware can propagate by stealing GitHub and npm credentials to push malicious updates and publish trojanized packages. Systems with this package installed should be considered fully compromised.
The weavedb-node-client npm package version 0.45.3 contains a malicious preinstall script that executes a packed native Linux binary. This binary acts as an infostealer targeting developer environments, harvesting credentials for cloud providers, source control, package registries, and cryptocurrency wallets. It also uses kernel-level rootkit techniques to hide its presence and exhibits worm-like behavior by stealing GitHub and npm credentials to propagate further malicious packages. Any system running npm install for this package on Linux is at risk of full compromise.
A critical authentication bypass vulnerability (CVE-2026-39831) exists in golang.org/x/crypto/ssh affecting FIDO/U2F security key types. The Verify() method fails to check the User Presence flag, allowing signatures generated without physical user interaction to be accepted. This flaw enables unauthorized use of hardware security keys without user touch unless mitigated by a specific extension in Permissions.Extensions. The vulnerability has a high CVSS score of 9.1 and impacts authentication security.
In the Linux kernel, the following vulnerability has been resolved: net/rds: handle zerocopy send cleanup before the message is queued A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket. The purge path currently infers zerocopy state from rm->m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages. However, zerocopy ownership is really determined by the presence of op_mmp_znotifier, regardless of whether the message has reached the socket queue. Capture op_mmp_znotifier up front in rds_message_purge() and use it as the cleanup discriminator. If the message is already associated with a socket, keep the existing completion path. Otherwise, drop the pinned page accounting directly and release the notifier before putting the payload pages. This keeps early send failure cleanup consistent with the zerocopy lifetime rules without changing the normal queued completion path.
The 'cb-wallet-data' npm package, published by an unaffiliated party but targeting a presumed Coinbase internal namespace, contains malicious code that sends an HTTPS GET request to an attacker-controlled endpoint during installation and import. This request transmits the package name and Node.js runtime version, exposing sensitive supply-chain reconnaissance data. The package version 0.0.1 is affected. Although the payload does not scrape credentials or environment variables, the presence of this beacon indicates a supply chain compromise risk. Removal of the package is recommended, but full system compromise is possible, necessitating secret and key rotation from a clean system.
The User Registration & Membership plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 5.1.5. This is due to the is_admin_creation_process() method relying solely on the presence of action=createuser in the $_REQUEST superglobal without performing any authentication or capability check. This makes it possible for unauthenticated attackers to bypass the admin approval requirement when registering new accounts via the fallback submission path.
Microdot is a minimalistic Python web framework. Prior to 2.6.1, the Response.set_cookie() method does not sanitize its string arguments, and in particular will not detect the presence of the \r\n sequence in them. This can be a potential source of header injection attacks. For a header injection attack through this issue to be possible, an attacker must first infiltrate the client (for example through an independent XSS attack), so that it can send malicious information that is destined to be stored in a cookie by the server on behalf of the victim. An attacker that infiltrates one client can only orchestrate a header injection attack for that client, all other clients that were not infiltrated are safe. This vulnerability is fixed in 2.6.1.