Malicious Code Injection in saubali-nanliui-iuyap: A Threat to npm Ecosystem

saubali-nanliui-iuyap Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165803: Malicious code in saubali-nanliui-iuyap (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 package 'saubali-nanliui-iuyap' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with random names, thereby inflating developer reputation scores. The malicious behavior of this package poses a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability originates from the package's design, which includes autopublish scripts that modify the package.json file to remove private flags and change version numbers. This allows the package to continuously generate and republish variants with Indonesian-themed names, polluting the npm registry. The ramifications include potential security risks for applications using this package, as it may lead to unintentional use of malicious code and compromise the integrity of the npm ecosystem.

How To Fix

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

npm uninstall saubali-nanliui-iuyap

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

Conclusion

The 'saubali-nanliui-iuyap' package represents a significant threat within the npm ecosystem due to its malicious behavior. Developers are urged to remove this package and monitor their projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for saubali-nanliui-iuyap →

Share this vulnerability

FAQ

It is a malicious npm package involved in a token reward campaign that manipulates the npm registry.

It can lead to the introduction of malicious code into your application, compromising its security and integrity.

You should uninstall the package immediately and check for any other potentially affected packages.

No, there is no patch for this specific package; the best course of action is to remove it entirely.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall saubali-nanliui-iuyap

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