Malicious Code Injection in uinsu-list-portal: npm Package Vulnerability
Summary
MAL-2025-169846: Malicious code in uinsu-list-portal (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 uinsu-list-portal package is part of the npm ecosystem, often utilized for managing lists and portals within applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms. This package is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages aimed at inflating developer reputation scores.
Vulnerability Detail
The vulnerability in uinsu-list-portal originates from its association with a malicious campaign that employs scripts to automatically generate and publish derivative packages. These scripts modify the package.json file by removing private flags, altering version numbers, and creating random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional code execution and dependency issues for developers who may unknowingly integrate these packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-list-portalIf 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, consider removing the uinsu-list-portal package from your project until a secure version is released. You can uninstall it using the command: npm uninstall uinsu-list-portal.
Conclusion
The uinsu-list-portal package has been identified as a vector for malicious code injection due to its involvement in a campaign aimed at inflating developer reputation scores. Developers should take immediate action to update or remove this package to safeguard their applications.
See every vulnerability recorded for uinsu-list-portal →
FAQ
The main risk is the potential for malicious code execution and the pollution of the npm registry, which can lead to security vulnerabilities in applications that depend on this package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help identify if your application is affected. You can also check using the Vulert playground at Vulert Scanner.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
While specific exploits have not been detailed, the nature of the vulnerability allows for potential code execution and dependency manipulation, which could be exploited by malicious actors.
Regularly check for updates from the package maintainers and utilize tools like Vulert to monitor your dependencies for any emerging vulnerabilities.
