Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@mntv-analysis/ui-componentsnpm

Advisory published Updated

@mntv-analysis/ui-components is a confirmed malicious npm package (MAL-2026-17870) that steals credentials and exfiltrates sensitive data (malicious version 50.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-17870
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @mntv-analysis/ui-components

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 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.

@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.

Malicious versions

1 flagged
50.1.1

Indicators of compromise (SHA-256)

bd96e684a44e791e753fd73119dd1a2d5b61f2f9fe69b16c86b7a11d9b266fcd

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @mntv-analysis/ui-components (version 50.1.1).

  2. If you installed it — respond

    @mntv-analysis/ui-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.

  3. Did it already run?

    If @mntv-analysis/ui-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

No. @mntv-analysis/ui-components on npm has been identified as a malicious package (version 50.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021492

References

Credits

  • Amazon Inspector · finder
  • InvisiRisk, Inc. · finder
  • SafeDep · finder

Detect & block this

O3 blocks @mntv-analysis/ui-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@mntv-analysis/ui-components (npm) malicious package — MAL-2026-17870 | O3 Security