Malicious Code Injection in uinsu-lost-dulakbu: A Threat to npm Packages
Summary
MAL-2025-169951: Malicious code in uinsu-lost-dulakbu (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'uinsu-lost-dulakbu' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores through the automatic generation and publishing of derivative packages.
Vulnerability Detail
The vulnerability in 'uinsu-lost-dulakbu' originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a compromised development environment, where developers may unknowingly use tainted packages, potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-lost-dulakbuIf 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 'uinsu-lost-dulakbu' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and trustworthiness of packages before including them in your project.
Conclusion
The 'uinsu-lost-dulakbu' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. By staying vigilant and using trusted packages, you can protect your applications from potential threats.
See every vulnerability recorded for uinsu-lost-dulakbu →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed the package, you should uninstall it immediately using 'npm uninstall uinsu-lost-dulakbu' and review your project's dependencies for any other potential vulnerabilities.
Yes, you should look for alternative packages that provide similar functionality but are verified and trusted within the community.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from reputable sources.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
