The npm package 'sc-announcer' version 99.9.1 is identified as malicious. It acts as a stub that depends on an off-registry tarball 'ltidisafe' fetched from an untrusted HTTPS URL without version pinning or integrity verification. Installing this package executes lifecycle scripts from the fetched tarball, potentially compromising the host system. The package communicates with domains linked to malicious activity. Systems with this package installed should be considered fully compromised, and all secrets and keys on those systems should be rotated immediately from a separate, secure machine.
The npm package 'fanarena-common' version 99.9.1 declares a dependency on 'ltidisafe' fetched directly from an external HTTPS URL rather than the npm registry. This external source lacks integrity checks and publisher verification, allowing the remote host to change the code executed during installation at any time. The package has been identified as malicious due to communication with a domain linked to malicious activity.
The npm package 'ccl-global-shopping' version 99.9.1 is identified as malicious. It declares a sole dependency via an unpinned HTTPS tarball URL, allowing the attacker to control the code executed during installation. The package itself contains an empty stub, making the external dependency the entire payload. It communicates with a domain linked to malicious activity. Any system with this package installed should be considered fully compromised, and secrets should be rotated immediately.
The npm package @an1mshnpmb9c84920/gat-scope-target-125ec19a version 1.0.0 is identified as malicious software. Although it contains only two files and no observable installer-harm behavior, its installation is considered a full system compromise. Any system with this package installed should be treated as fully compromised, with immediate rotation of all secrets and keys from a separate, secure system. Removal of the package alone does not guarantee elimination of all malicious software introduced.
The npm package @an1mshnpmb9c84920/pipe-dns-m19t2 contains malicious code embedded in its package.json metadata. Specifically, the repository.url field includes a shell command substitution that triggers a DNS lookup to an attacker-controlled domain, leaking the installer's host identity. The package itself has no legitimate functionality and appears to be part of a dependency confusion or manifest injection attack targeting internal npm tooling. Installation of this package compromises the host, potentially exposing all stored secrets and keys.
The npm package @an1mshnpmb9c84920/oidc-cross-cafb9d929e version 1.0.0 is identified as malicious. Although its code does not explicitly perform actions such as reading installer secrets, fetching or executing remote code, or opening backdoors, it is considered a severe threat. Installation of this package implies full compromise of the host system, requiring immediate secret and key rotation from a different machine. Removal of the package alone may not eliminate all resulting malicious software.
The npm package codex-setup versions 1.0.0 through 1.0.3 is identified as malicious software. Installation or execution of this package may lead to full compromise of the affected computer, requiring immediate secret and key rotation from a separate device. Despite one source indicating no suspicious behavior was detected in version 1.0.1, another authoritative source strongly warns that any system with this package should be considered fully compromised.
The npm package 'claude-desktop-setup' contains malicious code that redirects the Claude Desktop application's API communications to a typosquatted gateway controlled by an attacker. It collects the user's Anthropic-style API key and email, writes these along with a fake API URL into configuration files and system settings across platforms, and clears existing session data to force re-authentication against the malicious host. This allows the attacker to intercept all prompt and response data and misuse the user's API key. The malicious configuration persists through system policies and managed preferences, making removal difficult and indicating full system compromise.
The npm package 'chatgpt-desktop-setup' versions 1.0.2 and 1.0.3 contains malicious code that silently redirects ChatGPT Desktop and Codex CLI traffic to a third-party endpoint (https://api.vokes.in/v1). It disables sandbox protections and grants full filesystem access to the remote operator, enabling arbitrary code execution. Systems with this package installed should be considered fully compromised, and all stored secrets and keys must be rotated immediately.
The npm package api-anthropic impersonates Anthropic branding and redirects all Claude Code AI assistant traffic through an attacker-controlled proxy. It modifies user configuration files to route requests and pre-approves folder trust and external include prompts, enabling persistent interception of AI interactions and arbitrary file access without user consent. This results in a durable channel for exfiltrating sensitive data including prompts, code, file contents, and credentials.
The npm package @decoopus/chatgpt-setup version 1.0.2 contains malicious code that, when its CLI tool is run, modifies user configuration files to disable security controls and expands sandbox permissions to full filesystem access. It redirects the Codex model provider to an attacker-controlled gateway, allowing execution of instructions without user approval. This behavior is not documented in the README and only triggers via the documented CLI invocation. Systems with this package installed should be considered fully compromised, and all stored secrets and keys must be rotated immediately.
The npm package @decoopus/claude-setup contains malicious code that intercepts and exfiltrates Anthropic API keys and user data by redirecting requests to an attacker-controlled gateway. It modifies Claude Desktop configurations across multiple platforms, kills running Claude processes, deletes session and storage data, and forces re-authentication through the malicious gateway. The package also includes fabricated model names to mislead users. Any system with this package installed should be considered fully compromised.
The npm package '8i7pp4' version 0.0.0-stage is identified as malicious. Despite containing minimal files and no detected suspicious behaviors in static analysis, the package is flagged by a malware source as fully compromising any computer on which it is installed. Immediate secret and key rotation is advised, and the package should be removed. However, removal may not fully eliminate the compromise due to potential persistent malicious software.
The npm package array-inline version 2.0.5 is identified as malicious. Although static analysis and behavior tracing did not detect typical malicious activities such as credential access or network exfiltration, the package is considered fully compromising to any system where it is installed or running. Immediate secret and key rotation from a different machine is advised, and the package should be removed. However, removal may not fully eliminate the compromise as the attacker may have established persistent control.
The npm package 'array-inline-transform' version 1.0.0 is identified as malicious software. Although no static or dynamic analysis found evidence of credential theft, backdoors, or obfuscated payloads, the presence of this package on any computer indicates a full compromise. It is strongly advised to remove the package and rotate all secrets and keys from a separate, uncompromised machine to mitigate potential risks.
The npm package 'dsjklweuvhgsdcq' contains a malicious HTML page designed to mimic a Cloudflare Turnstile challenge with obfuscated JavaScript. It does not execute code on install or import but serves as a phishing lure when accessed via CDN URLs. Installation or running of this package compromises the host computer, potentially exposing all stored secrets and keys.
The npm package 'zxhgssiyluwxchn' version 1.0.0 contains a single HTML file that renders a Cloudflare Turnstile challenge page with heavily obfuscated JavaScript. This JavaScript reconstructs a URL impersonating cloudflare.com to serve a phishing landing page. The package does not execute code on installation, but serves as static hosting for browser-side phishing via npm CDN proxies. Installing this package does not run malicious code locally, but users fetching the HTML in browsers may be targeted for phishing. The package is considered malicious and should be removed.
The npm package 'vjkpwjxbvndelta' version 1.0.1 contains a malicious HTML file with heavily obfuscated inline script designed to mimic a Cloudflare Turnstile page. While the package does not execute code during installation or import, its presence indicates potential compromise. According to one source, any system with this package installed should be considered fully compromised, with immediate rotation of all secrets and keys recommended. The package appears to be used for static asset hosting abuse rather than a direct supply-chain attack. Removing the package alone may not eliminate all malicious components.
The npm package 'ticketcathayoct12' contains malicious code designed to impersonate a Cloudflare interstitial page with an embedded Turnstile widget and obfuscated script. It is associated with a Cathay Pacific-themed phishing campaign and serves HTML content through an npm-backed CDN. The package does not execute code on installation but targets end-user browsers loading the content via CDN URLs. Installing or running this package compromises the host computer, requiring immediate secret and key rotation and package removal.
The npm package 'nsdhjuiwqxmhsf1' version 1.0.0 is identified as malicious. It contains no executable JavaScript or TypeScript source code and no lifecycle hooks that run on installation. Instead, it serves an obfuscated HTML file mimicking Cloudflare Turnstile branding, likely intended for browser-based impersonation rather than direct code execution on developers' machines. Despite this, security sources warn that any system with this package installed should be considered fully compromised, recommending immediate secret and key rotation and package removal.