Malicious Code Injection in uinsu-losiat-dulaiku: A Threat to npm Packages
Summary
MAL-2025-169892: Malicious code in uinsu-losiat-dulaiku (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-losiat-dulaiku' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in 'uinsu-losiat-dulaiku' originates from its inclusion in a malicious campaign aimed at manipulating the npm ecosystem. The package contains scripts that alter the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior can lead to a compromised npm registry, making it difficult for developers to trust legitimate packages and potentially exposing them to further attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-losiat-dulaikuIf 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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor your dependencies. Ensure that you do not include 'uinsu-losiat-dulaiku' in your package.json or lock file. You can also use tools like Vulert to monitor your project for vulnerabilities without needing to access the code directly.
Conclusion
The 'uinsu-losiat-dulaiku' package poses a significant threat due to its malicious code designed to manipulate the npm ecosystem. It is essential for developers to be vigilant and regularly monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for uinsu-losiat-dulaiku →
FAQ
The package contains malicious code that modifies package.json files and republish variants to inflate developer reputation scores.
You can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to install any additional software.
You should immediately uninstall the package using 'npm uninstall uinsu-losiat-dulaiku' and review your other dependencies for security.
Yes, Vulert offers a playground where you can check if your application is affected by this vulnerability without any signup.
Failing to address this vulnerability can lead to a compromised npm registry, making it difficult to trust legitimate packages and exposing your application to further attacks.
