Malicious Code Injection in uinsu-lot-babiunaam Package

uinsu-lot-babiunaam Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169960: Malicious code in uinsu-lot-babiunaam (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 uinsu-lot-babiunaam package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package metadata and publishes variants to the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the uinsu-lot-babiunaam package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, thereby polluting the npm registry and potentially compromising the integrity of other packages. The ramifications include a loss of trust in the npm ecosystem and possible exploitation of affected applications.

How To Fix

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

npm uninstall uinsu-lot-babiunaam

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 the uinsu-lot-babiunaam package by adding it to your project's .npmrc file with the following line: package-lock=false. This will stop npm from installing any packages that are not explicitly defined in your package.json.

Conclusion

The uinsu-lot-babiunaam package contains malicious code that poses a significant risk to projects using it. Immediate action is required to uninstall the package and prevent further issues. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.

See every vulnerability recorded for uinsu-lot-babiunaam →

Share this vulnerability

FAQ

The uinsu-lot-babiunaam package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to the pollution of the npm registry and compromise your project's integrity.

You should uninstall the uinsu-lot-babiunaam package immediately using the command npm uninstall uinsu-lot-babiunaam and check your package-lock.json for any references.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json. You can check if your application is affected by visiting the Vulert playground.

Regularly audit your dependencies using tools like npm audit, and consider using Vulert to monitor your projects for vulnerabilities without requiring code access.

How To Fix

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

npm uninstall uinsu-lot-babiunaam

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