Malicious code in @mntv-analysis/ui-components (npm)

npm user 'conx3993' published this package in a dependency confusion campaign. It squats a name that looks like an internal package and uses version 50.1.1 so misconfigured resolvers pick it over the real one. Version 0.0.0-stage is an empty placeholder. A 'preinstall' hook runs 'index.js', which poses as an IP geolocation helper. On install it sends an HTTPS GET to attacker-controlled host realwbx.com (/ip.php?ip=8.8.8.8) with a hard-coded 'Authorization' value ('ba95f7810845c0347d6a88d157933c81') unique to this package, then discards the response. The token tells the operator which internal package name the victim installed, and the request reveals the victim's public egress IP.

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (bd96e684a44e791e753fd73119dd1a2d5b61f2f9fe69b16c86b7a11d9b266fcd)

@mntv-analysis/[email protected] is a hollow package whose only effective behavior on install is a tracking beacon. package.json declares scripts.preinstall: "node index.js", and index.js issues an HTTPS GET to https://realwbx.com/ip.php on npm install, carrying a hardcoded Authorization header value. The scoped @mntv-analysis/* name combined with an implausibly high 50.1.1 version, a placeholder README, no actual UI-component code, and a single-purpose beacon are the canonical dependency-confusion attack shape: the package exists to win internal-package resolution against a private @mntv-analysis scope and to signal successful landing on an installer host. Installation leaks the installer's public IP, timing, and the fact that the attacker's name squat resolved inside the target's build environment to realwbx.com, which is not a vendor endpoint associated with any UI-component library.

Source: ghsa-malware (a480513ccb709752092ebeed01c305c0d82b0a7e7d79fdebeb4eadb6957583be)

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.