@flex-ng/error-componentnpm

The @flex-ng/error-component package was published to the npm registry by user 'click2ai' (maintainer email [email protected]) as part of a dependency-confusion / reconnaissance campaign. The package name mimics the internal/private package naming convention of a target organization (the @flex-ng organizational scope) so that a misconfigured resolver installs this public lookalike instead of the intended private dependency.

The package declares a preinstall hook ("npm install @sentry/node && node examples/verify.js") that executes automatically at npm install time, before any application code runs. The bundled examples/verify.js initializes the @sentry/node client against a hardcoded, attacker-controlled Sentry DSN with sendDefaultPii enabled, resolves the installing host's public egress IP address by requesting Cloudflare's /cdn-cgi/trace endpoint (using a spoofed desktop-browser User-Agent to bypass bot challenges), then deliberately triggers a runtime exception and captures it. Flushing the event beacons the collected host telemetry (public IP plus Sentry default PII such as hostname, OS username and runtime/environment metadata) to the attacker's Sentry ingest endpoint at o4510485815754752.ingest.us.sentry.io.

Each impersonated namespace in the campaign beacons to a distinct Sentry project ID, letting the operator attribute successful installs to specific victim organizations — behaviour consistent with a dependency-confusion reconnaissance beacon rather than legitimate error monitoring. The install-time payload is byte-for-byte identical across all packages published by this account, differing only in the package name and the target DSN. This package's beacon targets Sentry project 4511632071262208.

package.json declares a preinstall hook ("npm install @sentry/node && node examples/verify.js") that runs on every npm install. examples/verify.js calls init() without a DSN; src/index.js falls back to a hardcoded DSN at https://o4510485815754752.ingest.us.sentry.io/4511632071262208 (author-controlled Sentry project). The script then resolves the installer's public egress IP (via a Cloudflare trace lookup in setUserFromPublicIp), enables sendDefaultPii: true, deliberately triggers an error, and ships the resulting event — carrying the installer's IP and host context — to the author's Sentry org. The installer never opts in: there is no DSN configuration step, the destination is hardcoded, and the README does not document this behavior. Additionally, the exported init() API hardcodes the same author DSN as its fallback, so any consumer who calls init() without explicit configuration silently relays their exceptions and PII to the author's Sentry account instead of their own.