Malicious Code Vulnerability in uinsnu-lotimi-killer Package

uinsnu-lotimi-killer Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169756: Malicious code in uinsnu-lotimi-killer (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-killer package is part of a broader campaign associated with the tea.xyz token reward system, which has been known to flood the npm registry with malicious packages. This package is designed to manipulate npm's publishing system, potentially impacting developers' reputations and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the uinsnu-lotimi-killer package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the automatic creation and publication of derivative packages. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall uinsnu-lotimi-killer

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, avoid using the uinsnu-lotimi-killer package and monitor your project for any dependencies that may have inadvertently included it. Regularly audit your package-lock.json file to identify and remove any malicious packages.

Conclusion

The uinsnu-lotimi-killer package presents a significant security risk due to its malicious code designed to manipulate npm's publishing system. Developers are advised to remove this package and monitor their projects for any dependencies that may have included it. Utilizing tools like Vulert can help in identifying vulnerabilities and maintaining the integrity of your applications.

See every vulnerability recorded for uinsnu-lotimi-killer →

Share this vulnerability

FAQ

It is a malicious npm package associated with a token reward campaign that modifies package metadata and publishes derivative packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without signup.

Using this package can lead to security vulnerabilities, reputation damage, and the pollution of the npm registry with malicious content.

Currently, there is no patched version available. The best course of action is to uninstall the package and monitor for updates.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the npm ecosystem.

How To Fix

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

npm uninstall uinsnu-lotimi-killer

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