MalwarePublished 6 Jul 2026Updated 14 Jul 2026

tme-xca-react (npm) · Malicious Code

Affects tme-xca-reactSource GCVE Database

Malicious package : remove tme-xca-react and rotate any secrets on hosts that installed it.

Data as of 14 Jul 2026, 09:27 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-10237

What to do

Remove tme-xca-react from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmtme-xca-react	Affected =3.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The tme-xca-react 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' 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. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (46077a15086044da0333de317d1d64309de37355e3630ad78126f28f0d6d096b) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (9658410180b55c2b87a859a01472dace3280720a84dedb244befa677caa2581d) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Impact

Systems that install the malicious tme-xca-react package version 3.0.0 are subject to telemetry data exfiltration during installation, potentially exposing sensitive host information such as public IP address, hostname, OS username, and runtime environment details to an attacker. This can lead to targeted follow-up attacks or further compromise. The presence of this package indicates a dependency confusion vulnerability in the victim's package resolution configuration. Full system compromise is possible if the attacker leverages the collected data or additional payloads. Removal of the package does not guarantee full remediation due to possible persistence mechanisms.

Defensive guidance

The recommended mitigation is to immediately remove the tme-xca-react package version 3.0.0 from all affected systems. Rotate all secrets and keys stored on compromised hosts from a secure, uncompromised environment. Review and correct dependency resolution configurations to prevent dependency confusion attacks, ensuring that private/internal packages cannot be overridden by public packages with similar names. Monitor for any suspicious activity resulting from this compromise. Since this is a malicious package, vendor advisories do not apply; remediation relies on removal and environment cleanup.

Summary

The tme-xca-react package (version 3.0.0) was published to the npm registry by an attacker as part of a dependency confusion and reconnaissance campaign targeting organizations using an internal 'tme' namespace. The package contains a preinstall hook that runs automatically during npm install, which installs @sentry/node and executes a script that collects sensitive telemetry data (public IP, hostname, OS username, runtime environment) from the host. This data is sent to a hardcoded attacker-controlled Sentry DSN, enabling the attacker to identify which organizations installed the package. The payload is identical across multiple packages published by the same attacker, differing only in package name and Sentry project ID. This malicious behavior is designed for reconnaissance rather than direct exploitation. The package version 3.0.0 is affected. There is no CVSS score or known exploit in the wild reported.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2026, 09:22 UTC

Technical details

References

Community reviews