The syft-acp-uikit package was published to the npm registry by an attacker impersonating an internal package naming convention to exploit dependency confusion. It contains a preinstall hook that runs a script initializing the @sentry/node client with a hardcoded attacker-controlled Sentry DSN and sendDefaultPii enabled. The script fetches the installing host's public egress IP from Cloudflare, triggers a runtime error, and sends a Sentry event containing the IP and default PII such as hostname, OS username, and environment metadata to the attacker's Sentry project. This telemetry beacon allows the attacker to identify which organizations installed the package. The package is part of a broader campaign using similar tactics and infrastructure.

The malicious package exfiltrates sensitive telemetry data including the public IP address, hostname, OS username, and runtime environment metadata from any system that installs it. This data is sent to an attacker-controlled Sentry project, enabling the attacker to perform reconnaissance on victim environments. While no direct code execution beyond the preinstall script is described, the automatic execution of this script during npm install can lead to unintended data leakage and potential further targeting based on the collected information.

No official patch or fix is available since this is a malicious package published to a public registry. The primary mitigation is to audit and restrict package sources to trusted registries and verify package provenance before installation. Organizations should ensure their dependency resolution is correctly configured to avoid dependency confusion attacks by prioritizing private/internal registries over public ones for internal package names. Additionally, monitoring for unexpected preinstall scripts in dependencies can help detect similar threats.