Advisory

MAL-2026-17869

Also known as: GHSA-f672-cw2f-69wr

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

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

Details

npm user 'conx3993' published this package in a dependency confusion campaign. It squats a name that looks like an internal package and uses version 99.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 ('2b6e9d1f4a7c0e3b8d5f2a9c6e1b4d7f') 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 (e19959148ce0529ebab1f6dbb0434f71b745b19d542d373b12577b208008ebfa)
The package's package.json declares a preinstall script that runs node index.js during npm install. index.js issues an HTTPS GET to https://realwbx.com/ip.php with a hardcoded Authorization header on every install, firing before any user code runs. The destination is unrelated to the declared @mntv-analysis scope and to any publisher-owned infrastructure, and the request's TCP source reveals the installer's public IP to that third-party host along with the hardcoded campaign token. The package otherwise ships a ~1KB index.js, a two-word README, and a vague description about IP/metadata lookup, providing no library surface that a consumer of a UI package would use. The shape is a victim-tagging install beacon inside a scope-styled lure, not a functional UI library.

Source: ghsa-malware (d1611044c74694feb27fecb3cf99f0b07b2a1972d1e99f4244a531bcac9943db)
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.

Severity

Not rated by the source.

Dates

Published
2026-10-13 00:00 UTC
Modified
2026-11-03 22:30 UTC

Affected packages and fixes

@mntv-analysis/ui

npm · All systems

Affected

  • introduced 0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences