Malicious Code Injection in mansila-iala-maolui: A Threat to npm Ecosystem
Summary
MAL-2025-159762: Malicious code in mansila-iala-maolui (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-iala-maolui' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of scripts that automatically generate and publish derivative packages, leading to potential abuse of the npm registry.
Vulnerability Detail
The vulnerability in 'mansila-iala-maolui' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages. The malicious payload is designed to continuously republish variants, making it difficult to track and mitigate the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mansila-iala-maolui
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-iala-maolui' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The 'mansila-iala-maolui' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and utilize tools like Vulert to safeguard their projects against similar vulnerabilities.
See every vulnerability recorded for mansila-iala-maolui →
FAQ
The vulnerability involves malicious code that modifies package.json and generates random package names, leading to npm registry pollution.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
It is advised to remove the package immediately and monitor your dependencies for any malicious activity.
Yes, Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Currently, there is no specific patch for 'mansila-iala-maolui', so the best course of action is to remove the package.