Malicious Code Injection in uinsu-lost-dauniu: A Threat to npm Ecosystem
Summary
MAL-2025-169934: Malicious code in uinsu-lost-dauniu (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-dauniu' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with a token reward campaign that has been known to flood the npm registry with malicious packages. Its primary functionality is to serve as a component of the tea.xyz token reward system, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in 'uinsu-lost-dauniu' originates from its association with a malicious campaign that generates and publishes derivative packages with randomized names. The malicious payload alters the package.json file to remove private flags, changes version numbers, and continuously republishes variants, leading to pollution of the npm registry. This can inflate developer reputation scores fraudulently and potentially introduce security risks to applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-lost-dauniu
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 remove the 'uinsu-lost-dauniu' package from your project by executing the command: 'npm uninstall uinsu-lost-dauniu'. This will prevent any malicious code from executing while you assess your dependencies.
Conclusion
The 'uinsu-lost-dauniu' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications from potential threats.
See every vulnerability recorded for uinsu-lost-dauniu →
FAQ
The malicious code modifies package.json files to remove private flags and generates random package names, which can lead to the pollution of the npm registry.
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.
Using compromised packages can lead to security vulnerabilities in your application, including unauthorized access, data breaches, and reputational damage.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.
If you cannot update the package, consider removing it from your project and replacing it with a secure alternative until a patch is available.