@mntv-analysis/workspaces-componentsnpm
Advisory published Updated
@mntv-analysis/workspaces-components is a confirmed malicious npm package (MAL-2026-17871) that steals credentials and exfiltrates sensitive data (malicious version 65.11.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @mntv-analysis/workspaces-components (npm)
What this malware does
npm user 'conx3993' published this package in a dependency confusion campaign. It squats a name that looks like an internal package and uses version 65.11.3 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 ('920ff204acf77aa813059be4f3141900') 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.
The package's package.json declares a preinstall script that executes index.js on every npm install. index.js issues an HTTPS GET to realwbx.com/ip.php with a hardcoded Authorization header, sending the installer's egress IP and install event to a host unrelated to the @mntv-analysis scope. The shipped code performs no other function; the package's only observable effect on install is this call-home. The combination of a stub package under an organization-looking scope, an install-time beacon to an unrelated third-party host, and a hardcoded auth token matches the dependency-confusion reconnaissance pattern used to tag installers of squatted internal names ahead of a follow-on payload.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @mntv-analysis/workspaces-components (version 65.11.3).
If you installed it — respond
@mntv-analysis/workspaces-components is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @mntv-analysis/workspaces-components was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- SafeDep · finder
Detect & block this
O3 blocks @mntv-analysis/workspaces-components-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.