Malicious Code Injection in uinsnu-lotimi-killneauar Package

uinsnu-lotimi-killneauar Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169758: Malicious code in uinsnu-lotimi-killneauar (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The uinsnu-lotimi-killneauar package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, which can mislead developers and inflate reputation scores for token rewards. The package's functionality is compromised by malicious scripts that manipulate its metadata.

Vulnerability Detail

The vulnerability in the uinsnu-lotimi-killneauar 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 can lead to the pollution of the npm registry, making it difficult for developers to trust the integrity of packages. The malicious payload is designed to continuously republish variants, exacerbating the issue.

How To Fix

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

npm uninstall uinsnu-lotimi-killneauar

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-killneauar package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The uinsnu-lotimi-killneauar package is compromised by malicious code that alters its metadata and repopulates the npm registry with potentially harmful variants. It is crucial to remove this package and monitor your project for vulnerabilities to maintain security.

See every vulnerability recorded for uinsnu-lotimi-killneauar →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the pollution of the npm registry, making it difficult to trust the integrity of packages and potentially introducing malicious code into your project.

You should uninstall the package immediately using the command npm uninstall uinsnu-lotimi-killneauar and monitor your project for any other vulnerabilities.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can check your application for vulnerabilities without signing up at the Vulert playground.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review the packages you include in your project for any known issues.

How To Fix

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

npm uninstall uinsnu-lotimi-killneauar

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