Malicious Code Injection in uinsnu-lotimi-killear: A Threat to npm Packages

uinsnu-lotimi-killear Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169755: Malicious code in uinsnu-lotimi-killear (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 package 'uinsnu-lotimi-killear' is part of a malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is primarily centered around automating the publication of these malicious packages, posing a significant risk to developers and users relying on npm packages.

Vulnerability Detail

The vulnerability arises from the presence of malicious code within the 'uinsnu-lotimi-killear' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this issue is linked to the tea.xyz token reward campaign, which aims to exploit the npm registry by flooding it with these harmful packages. The ramifications include potential security risks for applications using these packages, as they may inadvertently incorporate malicious code, leading to data breaches or system compromises.

How To Fix

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

npm uninstall uinsnu-lotimi-killear

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 measure, you can avoid using the 'uinsnu-lotimi-killear' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The 'uinsnu-lotimi-killear' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the affected package, and utilize tools like Vulert for ongoing monitoring of their applications.

See every vulnerability recorded for uinsnu-lotimi-killear →

Share this vulnerability

FAQ

It is a malicious npm package linked to a token reward campaign that automates the publication of harmful derivative packages.

If your application uses this package, it may inadvertently include malicious code, leading to security risks such as data breaches.

Immediately uninstall the package using 'npm uninstall uinsnu-lotimi-killear' and monitor your application for any unusual behavior.

Yes, you can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall uinsnu-lotimi-killear

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