Malicious Code Injection in uinsu-losit-bik Package: A Threat to npm Ecosystem
Summary
MAL-2025-169896: Malicious code in uinsu-losit-bik (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 uinsu-losit-bik package is part of a broader campaign targeting the npm ecosystem, specifically associated with the tea.xyz token reward initiative. This package, like others in its category, is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, which poses a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the uinsu-losit-bik package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only pollutes the npm registry but also compromises the security and reliability of the packages within it, potentially leading to further exploitation by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-losit-bikIf 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-losit-bik package altogether until a patch is released. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.
Conclusion
The uinsu-losit-bik package presents a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to remain vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for uinsu-losit-bik →
FAQ
The uinsu-losit-bik package is part of a malicious campaign that aims to inflate developer reputation scores within the npm ecosystem.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity and security of your project's dependencies.
You should update the package to the latest version or remove it from your project until a patch is available.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring an account.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
