Malicious code in @mntv-analysis/ui (npm)
Published Sources: OSV (Schadpakete)
- Malicious package
What is affected, what to do
Uninstall the package, isolate affected environments and rotate credentials that were available during installation.
Not sure whether and how you are affected? Ask a question about this vulnerability
Malicious package
npm@mntv-analysis/ui
“@mntv-analysis/ui” is registered as malicious in the npm repository. Anyone who installed the package should uninstall it immediately, isolate affected environments and rotate credentials that were present during installation.
Affected versions (1)
- 99.1.1
purl: pkg:npm/%40mntv-analysis/ui
Sources (1)
amazon-inspector
IN-MAL-2026-021491Versions from this source: 99.1.1
sha256: e19959148ce0529ebab1f6dbb0434f71b745b19d542d373b12577b208008ebfa
The OSSF `malicious-packages` namespace lists packages flagged as malicious by static analysis or sandbox detonation. An entry here is a confirmed finding, not a suspicion.
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
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.