Malicious code in @edgecommons/edgecommons (npm)

The @edgecommons/edgecommons package was published by a malicious actor as part of a dependency-confusion campaign targeting organizations that use private scoped packages. The package name mimics an internal namespace to cause accidental installation. It declares a preinstall hook that installs @sentry/node and runs a script which initializes a Sentry client with a hardcoded attacker-controlled DSN and sendDefaultPii enabled. The script obtains the host's public IP by querying Cloudflare's trace endpoint with a spoofed User-Agent, triggers a runtime exception, and captures it to send telemetry data (public IP, hostname, OS username, runtime metadata) to the attacker's Sentry project. Each impersonated namespace beacons to a unique Sentry project ID, allowing attribution of installs to specific organizations. This package shares payload code and infrastructure with a prior campaign named 'click2ai' and is part of a broader reconnaissance effort rather than direct exploitation.

The impact is primarily information disclosure of host telemetry during npm install time. The attacker gains knowledge of the victim's public IP address, hostname, OS username, and runtime environment metadata. This data can be used for reconnaissance to identify and profile victim organizations that mistakenly install the malicious package due to dependency confusion. There is no indication of further exploitation or payload delivery beyond this telemetry beaconing.

Users should audit and verify all package dependencies, especially scoped packages that mimic internal namespaces. Avoid misconfigured npm resolvers that allow public packages to override private/internal dependencies. Remove any installations of the @edgecommons/edgecommons package and related malicious packages from the 'click2ai' campaign. Since this is a malicious package published to the public npm registry, the best mitigation is to ensure private package namespaces are properly configured and not resolvable from the public registry. There is no official patch since this is a malicious package, but remediation involves removing the package and correcting dependency resolution configurations.