Malicious Code Detected in uinsu-loti-baam: A Threat to npm Users
Summary
MAL-2025-169997: Malicious code in uinsu-loti-baam (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 'uinsu-loti-baam' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package configurations and repopulates the npm registry with potentially harmful variants.
Vulnerability Detail
The vulnerability in 'uinsu-loti-baam' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-loti-baamIf 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 measure, you can avoid using the 'uinsu-loti-baam' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes to package.json.
Conclusion
The 'uinsu-loti-baam' package poses a significant threat due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.
See every vulnerability recorded for uinsu-loti-baam →
FAQ
The uinsu-loti-baam package contains malicious code that modifies package configurations and floods the npm registry with derivative packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed the uinsu-loti-baam package, it is advisable to remove it immediately and check for any unauthorized changes in your project.
Yes, consider using other npm packages that offer similar functionality but do not have a history of malicious behavior. Always review package reputations before installation.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.
