Malicious Code Injection in uinsu-lost-daunaiku: A Threat to npm Ecosystem
Summary
MAL-2025-169932: Malicious code in uinsu-lost-daunaiku (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-lost-daunaiku' 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 known to flood the npm registry with malicious packages. The primary functionality of this package is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in 'uinsu-lost-daunaiku' originates from its design to include autopublish scripts that automatically generate and publish derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which leads to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly install these compromised packages, as they may inadvertently contribute to the spread of malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-lost-daunaikuIf 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-daunaiku' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'uinsu-lost-daunaiku' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry. It is essential for developers to be vigilant, regularly update their packages, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for uinsu-lost-daunaiku →
FAQ
The primary issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed the package, you should remove it immediately and update your project to eliminate any potential risks.
Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Using compromised packages can lead to security breaches, data loss, and can compromise the integrity of your software projects.
