The npm package animatecss-tailwind-graphic version 2.0.6 is linked to a malicious campaign involving fake job interviews. It depends on a private scoped package that is not publicly accessible and requires an npm token found in a lure repository, enabling execution of hidden code when the plugin is loaded in Tailwind CSS. The public tarball itself contains no install scripts or network code, and no direct harmful behavior was observed in the shipped package contents. Multiple similar packages were published under various accounts over a period of months.
The npm package animatecss-tailwind-binary version 2.0.6 is part of a malicious campaign involving fake job interview lures. The package itself contains no install scripts or network code, but it depends on a private scoped package that requires an npm token to access. This private dependency, which was not retrieved during analysis, contains the malicious payload that executes when the Tailwind CSS plugin loads during development server startup. Multiple related malicious packages were published under various accounts over a period from July to October 2026.
The animate-twcss-pack version 2.0.6 is a Tailwind CSS plugin linked to a fake job interview campaign involving malicious packages. It depends on a private scoped package that is not publicly accessible, which could deliver malicious code when the plugin is loaded. However, analysis found no evidence of harmful behavior such as exfiltration, credential theft, or remote code execution in the publicly available package.
The npm package animate-twcss-bridge version 2.0.6 is identified as malicious and linked to a fake job interview campaign. It depends on a private scoped package that requires an npm token to resolve, which can execute code when the Tailwind CSS plugin loads. The publicly available tarball does not contain install scripts or network code, and the malicious payload resides in the private dependency. Multiple related malicious packages were published under various accounts over a period of months. No direct lifecycle script execution or network communication is present in the shipped contents.
The animate-tailwind-kit npm package versions 3.0.1 and 3.0.4 are linked to a malicious campaign involving a private dependency that delivers malicious code when the plugin is loaded in Tailwind CSS configurations. The public package itself contains no installer scripts or network code, but it requires a private scoped package that is not publicly accessible and relies on an npm token committed in a lure repository. This private dependency executes code during development server startup. Multiple related malicious packages were published over several months under various accounts.
The npm package tailwind-fabric versions 3.0.1 and 3.0.4 is associated with a malicious campaign involving a private dependency that executes code when the plugin is loaded. The payload resides in a private scoped package that requires an npm token to access, preventing direct retrieval from the public registry. The publicly published tarball contains no install scripts or network code, and no direct malicious behavior was observed in the examined package code paths. Multiple related packages were published under various accounts over a period of months.
The npm package signalledger-diagnostics version 2.0.6 is identified as part of a malicious campaign involving fake job interview lures. The package is a Tailwind CSS plugin that depends on a private scoped package requiring an npm token, which delivers the actual malicious payload when the plugin is loaded during development. The publicly available tarball does not contain install scripts or network code, and no direct malicious behavior was observed in the shipped files. Multiple similar packages were published under various accounts over a period of months.
The signalledger-bridge npm package version 2.0.6 is associated with a malicious campaign involving fake job interview lures. The package itself contains no install scripts or network code, but it depends on a private scoped package that delivers the malicious payload when the plugin is loaded in Tailwind CSS. The private dependency is not publicly accessible and requires an npm token, which was exposed in the lure repository. Multiple related malicious packages were published over several months under different accounts.
The animatecss-tailwind-vectrix npm package versions 2.0.6 and 2.0.7 are part of a malicious campaign involving fake job interview lures. The package depends on a private scoped package that requires an npm token to access, which can execute code when the Tailwind CSS plugin loads during development server startup. The public tarball itself contains no install scripts or network code, and the private dependency was not retrieved for analysis. Multiple related malicious packages were published under various accounts between July and October 2026.
The animatecss-tailwind-presets npm package versions 1.0.0 and 2.0.3 are linked to a malicious campaign involving a private dependency that delivers malicious code when the plugin is loaded in Tailwind CSS configurations. The public package itself contains no direct installer-facing malicious behavior, but it requires a private scoped package that is not publicly accessible and contains the actual payload. Multiple related packages were published under different accounts over a period of several months.
The animatecss-tailwind-plugin version 2.0.6 is a malicious Tailwind CSS plugin linked to a fake job interview campaign. It includes a private scoped dependency that requires an npm token to access, which delivers malicious code executed when the plugin loads in tailwind.config.js and the development server starts. The published package itself contains no install scripts or network code, and the malicious payload resides in the private dependency. Multiple similar malicious packages were published under various accounts over a recent period.
The animatecss-tailwind-helper package version 2.0.6 is part of a malicious campaign involving fake job interview lures. It is a Tailwind CSS plugin that depends on a private scoped package only accessible with a committed npm token, which delivers malicious code when the plugin is loaded. The public tarball itself contains no install scripts or network code, and the payload resides in the private dependency. Multiple similar malicious packages were published under various accounts over a period of months. The shipped files do not include installer secrets, network communication, or persistence mechanisms.
The npm package @pkgship/frpc-linux-arm64 version 0.71.0 contains malicious code. It is a platform-specific distribution that installs a prebuilt native binary for Linux ARM64 systems. Although the package does not execute code during installation or perform network callbacks, its presence indicates a full compromise of the affected system. Any computer with this package installed should be considered fully compromised, and all secrets and keys on that system should be rotated immediately. Removal of the package alone may not eliminate all malicious software introduced.
The npm package 'rootaccessxvv-bbmarker' version 1.0.2 contains malicious code that executes during installation. It runs a postinstall script that collects host identifiers and system information, then exfiltrates this data to an attacker-controlled webhook URL. This behavior constitutes a supply-chain attack by automatically sending sensitive metadata without user consent.
The CKAN MCP server's DataStore Table UI resource fails to validate the origin of inbound postMessage events and sends outbound messages with a wildcard target origin '*'. This allows any window or frame that can reach the document to inject arbitrary data into the table, causing content spoofing and interference with the UI's handshake process. The vulnerability does not allow script injection but can cause display spoofing and disrupt user experience. The issue is considered low severity due to its dependency on the embedding context and limited direct remote exploitability.
The npm package @beloved-lenora/opencode-orchestrator contains malicious code that fully compromises any computer on which it is installed or running. Removal of the package does not guarantee elimination of all malicious software introduced. Immediate rotation of all secrets and keys stored on the affected computer is strongly advised.
The npm package '@beloved-lenora/opencode-btw' contains malicious code that can fully compromise any computer on which it is installed or running. This compromise includes potential unauthorized access to secrets and keys stored on the affected system. Removal of the package does not guarantee complete eradication of the malicious software, as the attacker may have established persistent control.
The npm package @beloved-lenora/opencode-goal contains malicious code that fully compromises any computer on which it is installed or running. It can lead to complete system compromise, requiring immediate rotation of all secrets and keys from a different, uncompromised machine. Removal of the package alone does not guarantee elimination of all malicious software introduced by it.
The npm package @beloved-lenora/opencode-stats contains malicious code that can fully compromise any computer on which it is installed or running. The compromise may lead to unauthorized access to secrets and keys stored on the affected system. Removal of the package alone does not guarantee elimination of all malicious software introduced by it. Immediate rotation of all secrets and keys from a separate, uncompromised device is strongly recommended.
The npm package @beloved-lenora/opencode-todo contains malicious code that fully compromises any computer on which it is installed or run. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted machine. Removing the package alone does not guarantee removal of all malicious software introduced by it.