The @idms-corp/auth-ui package published on npm by user 'click2ai' is a malicious package designed for dependency confusion reconnaissance. It mimics an internal organizational package namespace to be installed mistakenly by misconfigured package resolvers. The package declares a preinstall hook that runs a script initializing the @sentry/node client with a hardcoded attacker-controlled DSN, enabling the collection and exfiltration of the installer's public IP address and default personally identifiable information (PII) such as hostname, OS username, and runtime metadata. This data is sent to the attacker's Sentry project endpoint. The package also includes a fallback DSN that causes any consuming application calling init() without specifying a DSN to send error telemetry to the attacker. The package contains no legitimate authentication or UI functionality despite its name and scope. Versions 0.0.0 and 1.0.0 are affected. The malicious behavior enables attribution of successful installs to specific victim organizations and potential compromise of sensitive host information.

Installation of this package results in the exfiltration of the host's public IP address and default PII to an attacker-controlled Sentry endpoint. Additionally, applications using this package without specifying their own DSN may unknowingly send error and environment telemetry, including stack traces and request data, to the attacker. This compromises confidentiality and privacy of the affected systems. The presence of this package indicates a successful dependency confusion attack, and any system with it installed should be considered fully compromised. Secrets and keys on the system should be rotated immediately from a different, trusted machine.

No official patch or fix is available for this malicious package. The primary mitigation is to remove the package immediately from all affected systems. Given the nature of the compromise, it is critical to consider the affected systems fully compromised and rotate all secrets and credentials from a secure environment. Organizations should audit their package resolution configurations to prevent dependency confusion attacks by ensuring private packages are resolved correctly and not overridden by public packages with similar names. Monitoring and blocking suspicious packages published under internal namespace impersonations is recommended.