Malicious Code Injection in uinsu-losiat-dukl Package: A Threat to npm Ecosystem
Summary
MAL-2025-169888: Malicious code in uinsu-losiat-dukl (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-losiat-dukl package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that have randomized names. This behavior not only undermines the integrity of the npm ecosystem but also poses significant risks to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in the uinsu-losiat-dukl package originates from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to developers inadvertently using compromised packages, which may contain harmful code or scripts that could affect their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-losiat-duklIf 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-losiat-dukl package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The uinsu-losiat-dukl package poses a significant security risk due to its malicious code injection and association with a harmful campaign. It is essential for developers to be vigilant and remove this package from their projects. Regular audits and the use of monitoring tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for uinsu-losiat-dukl →
FAQ
The uinsu-losiat-dukl package is an npm package that has been identified as part of a malicious campaign aimed at flooding the npm registry with compromised packages.
Using the uinsu-losiat-dukl package can expose your application to malicious code, which may lead to security breaches or data loss.
You should immediately uninstall the uinsu-losiat-dukl package using the command npm uninstall uinsu-losiat-dukl.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
