Malicious Code Injection in uinsnu-lotimi-klu Package: npm Vulnerability Overview

uinsnu-lotimi-klu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169760: Malicious code in uinsnu-lotimi-klu (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The uinsnu-lotimi-klu package 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 facilitate the distribution of JavaScript libraries, but it has been compromised to serve malicious purposes, including the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the uinsnu-lotimi-klu package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to pollution of the npm registry. The malicious payload can potentially compromise the integrity of applications relying on this package, allowing for further exploitation.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall uinsnu-lotimi-klu

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 avoid using the uinsnu-lotimi-klu package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The uinsnu-lotimi-klu package has been identified as a malicious entity within the npm ecosystem, posing significant risks to applications that utilize it. Immediate action is required to mitigate these risks by uninstalling the package and monitoring for vulnerabilities using tools like Vulert.

See every vulnerability recorded for uinsnu-lotimi-klu →

Share this vulnerability

FAQ

The uinsnu-lotimi-klu package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of derivative packages.

This vulnerability can compromise the integrity of your application by introducing malicious code that may lead to further exploitation or data breaches.

You should uninstall the uinsnu-lotimi-klu package immediately and check for any dependencies that may rely on it. Consider updating to a secure alternative.

Yes, you can use Vulert to monitor your package-lock.json for open-source vulnerabilities in real-time without requiring access to the code or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall uinsnu-lotimi-klu

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback