tme-xca@3.0.0

The tme-xca package was published to the npm registry by user 'click2ai' (maintainer email privatek3m@protonmail.com) as part of a dependency-confusion / reconnaissance campaign. The package name mimics the internal/private package naming convention of a target organization (a 'tme' (Travel Mall / TME-style) internal namespace) 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 4511630928838656. --- ## Source: amazon-inspector (6012c6bcd17a7184340cb8ed6dc94d58d97b92826c0f510d81ddebd4160d86f0) On `npm install`, the package's preinstall hook executes `examples/verify.js`, which initializes Sentry against a hardcoded author-controlled DSN (project `o4510485815754752.ingest.us.sentry.io/4511630928838656`), fetches the installer's public IP from Cloudflare's trace endpoint, attaches it as the Sentry user identity, deliberately throws to generate an event, and flushes upstream. Every install of this version transmits the installer's public egress IP and host-side error context to a fixed remote destination the installer did not choose. Separately, `src/index.js` hardcodes the same DSN as `DEFAULT_DSN` and enables `sendDefaultPii: true`; consumers who call the advertised `init`/`check`/`reportError` API without supplying their own DSN or setting `SENTRY_DSN` silently route their captured exceptions and PII into the author's Sentry account. The relay is not the documented purpose of an error-reporting helper, and the destination is hardcoded to the author rather than configured by the installer.