The box-react-uix package published on npm by user 'click2ai' is a malicious package designed for dependency confusion attacks. It declares a preinstall hook that runs automatically during npm install, which installs @sentry/node and executes a script that initializes a Sentry client with a hardcoded attacker-controlled DSN. This script collects the installer's public IP address via Cloudflare's trace endpoint, attaches default PII such as hostname and OS username, and sends this telemetry to the attacker's Sentry project. The package name mimics an internal 'box' namespace to trick misconfigured resolvers into installing it instead of legitimate private packages. The payload is identical across all packages from this attacker, differing only in the targeted Sentry project ID, enabling attribution of installs to specific victims. The runtime initialization also defaults to the attacker’s Sentry endpoint if no DSN is provided, silently exfiltrating errors and PII. The package contains no legitimate UI code, consistent with a lure and reconnaissance tactic. The affected version is 18.6.91. There is no evidence of known exploits in the wild, but any system with this package installed should be considered fully compromised.

Installing the box-react-uix package version 18.6.91 results in automatic execution of a preinstall script that collects and exfiltrates the host's public IP address and personally identifiable information (PII) such as hostname and OS username to an attacker-controlled Sentry endpoint. This compromises the confidentiality of the host environment and enables the attacker to identify and attribute installations to specific organizations. The runtime code also silently sends errors and PII to the attacker if the consumer does not provide their own Sentry DSN, increasing the risk of ongoing data leakage. According to the ghsa-malware source, any computer with this package installed or running should be considered fully compromised, requiring immediate secret and key rotation from a different machine. Removal of the package alone does not guarantee full remediation due to potential further compromise.

There is no official patch or fix available for this malicious package. The best mitigation is to avoid installing the box-react-uix package and audit your dependency configurations to prevent dependency confusion attacks by ensuring private packages are resolved correctly. If this package has been installed, remove it immediately and consider the host fully compromised. Rotate all secrets and keys stored on the affected host from a separate, trusted machine. Monitor for any signs of further compromise and rebuild affected systems if necessary. Review and tighten npm resolver configurations to prevent installation of similarly named malicious packages.