Malicious Code Injection in messi-tueda-sddsf: A Threat to npm Ecosystem
Summary
MAL-2025-160363: Malicious code in messi-tueda-sddsf (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 package 'messi-tueda-sddsf' is part of a broader campaign targeting the npm ecosystem, where malicious packages are designed to inflate developer reputation scores through automated scripts. These packages typically generate and publish numerous derivative versions with randomized names, contributing to registry pollution and undermining the integrity of the npm repository.
Vulnerability Detail
The vulnerability in 'messi-tueda-sddsf' stems from its association with the tea.xyz token reward campaign, which employs autopublish scripts to manipulate the package.json file. This manipulation removes private flags, alters version numbers, and creates random package names, leading to a significant risk of reputation damage for developers and potential exploitation of the npm registry. The malicious nature of this package can lead to unintentional installations by users, further spreading the threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall messi-tueda-sddsfIf 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 prevent the installation of this malicious package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid automatic installations of potentially harmful packages.
Conclusion
The 'messi-tueda-sddsf' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their projects from potential exploitation.
See every vulnerability recorded for messi-tueda-sddsf →
FAQ
The main risk is that it can manipulate your project's package.json, leading to unauthorized changes and potential security vulnerabilities.
You can use Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.
Immediately uninstall the package using 'npm uninstall messi-tueda-sddsf' and review your project's dependencies for any other malicious packages.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time, ensuring your application remains secure.
Regularly audit your dependencies, use tools like Vulert for monitoring, and avoid installing packages from untrusted sources.
