Malicious Code Injection in messi-di-fsae: A Threat to npm Users
Summary
MAL-2025-160305: Malicious code in messi-di-fsae (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The 'messi-di-fsae' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. Its primary function is to facilitate the distribution of JavaScript code, but it has been compromised to include harmful scripts that manipulate package metadata and flood the npm registry with derivative packages.
Vulnerability Detail
The vulnerability in 'messi-di-fsae' originates from its association with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. The malicious code within this package modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry, potentially affecting other developers and users relying on npm for package management.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall messi-di-fsaeIf 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-di-fsae' package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The 'messi-di-fsae' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert. Staying informed and proactive can help safeguard your applications from such threats.
See every vulnerability recorded for messi-di-fsae →
FAQ
The 'messi-di-fsae' package is an npm package that has been identified as malicious, part of a campaign to exploit the npm registry.
This vulnerability can compromise your project's integrity by introducing malicious code that alters package metadata and floods the npm registry.
You should uninstall the package immediately using 'npm uninstall messi-di-fsae' to mitigate the risk.
Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability.
