The @logdna-web/styles package was published by an attacker impersonating the LogDNA namespace to exploit dependency confusion. It includes a preinstall hook that installs @sentry/node and runs a script to collect the installing machine's public IP (via Cloudflare's trace endpoint) and other PII, then deliberately triggers an exception to send this data to a hardcoded attacker-controlled Sentry DSN. Additionally, the package's init() function silently forwards error reports and user context to the attacker's Sentry project if no explicit DSN is provided, enabling ongoing data exfiltration. This campaign uses distinct Sentry project IDs per impersonated namespace to track successful installs per victim organization. The package version 0.8.40 is affected.

Installation of this package results in exfiltration of the host machine's public IP address, hostname, OS username, and runtime environment metadata to an attacker-controlled Sentry project without user consent or disclosure. The preinstall script runs automatically during npm install, potentially before any application code, enabling early reconnaissance. Additionally, any use of the package's init() function without explicit configuration causes silent routing of error and user data to the attacker. This compromises confidentiality and privacy of the affected systems and may facilitate further targeted attacks. The package is considered fully compromising to any system where it is installed or running.

No official patch or remediation is currently available. Users should immediately remove the @logdna-web/styles package version 0.8.40 from their projects. Rotate all secrets and keys stored on affected machines from a separate, uncompromised device. Review and audit dependency configurations to prevent dependency confusion attacks, including verifying package scopes and sources. Avoid installing packages from untrusted or suspicious namespaces. Monitor for any unauthorized network activity related to Sentry endpoints controlled by unknown parties. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.