tme-error (npm) · Malicious Code
Affects tme-errorSource GCVE Database
Malicious package : remove tme-error and rotate any secrets on hosts that installed it.
Data as of 14 Jul 2026, 09:37 UTC
Malicious package
Published to npm · OSV MAL-2026-10235
What to do
Remove tme-error 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-error | Affected
| 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-error npm package, published by a malicious actor, impersonates an internal package namespace to exploit dependency confusion. It includes a preinstall hook that executes code during npm install, sending the installer's public IP, hostname, username, and runtime metadata to an attacker-controlled Sentry endpoint without user consent. This behavior enables reconnaissance on victims and potential data exfiltration. The package also silently redirects error reporting to the attacker's Sentry project if consumers call its init() function without specifying their own DSN. The affected version is 2.8.42. Removal alone may not fully remediate the compromise, and secrets should be rotated.