Malicious Code Injection in messi-urfat-dissa Package - npm Vulnerability

messi-urfat-dissa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160390: Malicious code in messi-urfat-dissa (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The messi-urfat-dissa package is part of the npm ecosystem, often used for various JavaScript applications. This package has been identified as part of a broader campaign that aims to manipulate the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to alter package metadata and republish variants, which can mislead developers and inflate reputation scores for token rewards.

Vulnerability Detail

The vulnerability originates from the package's design, which includes scripts that automatically modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these manipulated packages, as they may inadvertently introduce vulnerabilities into their applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall messi-urfat-dissa

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can avoid using the messi-urfat-dissa package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The messi-urfat-dissa package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for messi-urfat-dissa →

Share this vulnerability

FAQ

messi-urfat-dissa is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the messi-urfat-dissa package immediately and check for any other affected packages in your project.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall messi-urfat-dissa

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback