Malicious Code Injection in mansila-tiola-mazoala: A Threat to npm Ecosystem
Summary
MAL-2025-159854: Malicious code in mansila-tiola-mazoala (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 'mansila-tiola-mazoala' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in 'mansila-tiola-mazoala' originates from its involvement in the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and creating random package names. This not only clutters the npm registry but also poses risks of dependency confusion and potential exploitation of users who may unknowingly install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mansila-tiola-mazoala
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 'mansila-tiola-mazoala' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.
Conclusion
The 'mansila-tiola-mazoala' package poses significant security risks due to its malicious code designed to manipulate npm's publishing system. It is essential for developers to take immediate action by removing the package and ensuring their projects are secure. Utilizing tools like Vulert can help maintain awareness of vulnerabilities in open-source software.
See every vulnerability recorded for mansila-tiola-mazoala →
FAQ
The main risk is the injection of malicious code that can alter your project's dependencies and potentially lead to security breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using 'npm uninstall mansila-tiola-mazoala' and review your project for any other potentially vulnerable packages.
Yes, consider searching for other npm packages that provide similar functionality but have a verified reputation and no known vulnerabilities.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from reputable sources.