Malicious Code Injection in uinsnu-lotimi-kil Package

uinsnu-lotimi-kil Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169752: Malicious code in uinsnu-lotimi-kil (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 Your last release was probably never penetration tested 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-kil package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. Its primary functionality revolves around inflating developer reputation scores for token rewards, but it has been compromised to include malicious scripts.

Vulnerability Detail

The vulnerability in the uinsnu-lotimi-kil package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can affect developers by inflating their reputation scores fraudulently and may lead to the installation of compromised packages by unsuspecting users.

How To Fix

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

npm uninstall uinsnu-lotimi-kil

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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. You can also utilize Vulert to check for vulnerabilities in your application without requiring access to the code or installation. Use the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability.

Conclusion

The uinsnu-lotimi-kil package has been identified as a vector for malicious code injection, posing significant risks to developers and their projects. Immediate action is required to remove this package and safeguard against potential threats. Utilizing tools like Vulert can enhance your ability to monitor and manage open-source vulnerabilities effectively.

See every vulnerability recorded for uinsnu-lotimi-kil →

Share this vulnerability

FAQ

The uinsnu-lotimi-kil package is an npm package involved in a token reward campaign that has been compromised to include malicious scripts.

This vulnerability can lead to the installation of malicious packages, compromising your project's integrity and potentially affecting your reputation as a developer.

You should immediately remove the uinsnu-lotimi-kil package from your project and monitor for any updates or patches that may be released.

Yes, Vulert can monitor your package-lock.json file and alert you in real-time for any open-source vulnerabilities, including this one.

Regularly monitor your dependencies, use tools like Vulert for vulnerability detection, and stay updated on best practices for package management.

How To Fix

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

npm uninstall uinsnu-lotimi-kil

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