Malicious Code Injection in uinsu-ls-dingks: A Threat to npm Ecosystem
Summary
MAL-2025-170063: Malicious code in uinsu-ls-dingks (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-ls-dingks is part of a broader campaign that exploits the npm ecosystem by flooding it with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The malicious nature of this package lies in its ability to alter package metadata and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in uinsu-ls-dingks originates from its association with the tea.xyz token reward campaign, which employs autopublish scripts to generate and publish derivative packages with randomized names. This malicious payload modifies the package.json file by removing private flags, altering version numbers, and creating random package names. The continuous republishing of these variants can lead to significant pollution of the npm registry, affecting developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-ls-dingksIf 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-ls-dingks package and monitor your project's dependencies for any indirect usage. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The uinsu-ls-dingks package poses a significant threat to the npm ecosystem due to its malicious behavior of altering package metadata and republishing variants. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.
See every vulnerability recorded for uinsu-ls-dingks →
FAQ
uinsu-ls-dingks is an npm package that has been identified as malicious, part of a campaign to manipulate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, potentially affecting the integrity and security of your project by introducing unwanted packages.
You should uninstall the package immediately using 'npm uninstall uinsu-ls-dingks' and check your dependencies for any reliance on it.
Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities without requiring access to the code or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
