Malicious Code Injection in salabunli-nibia-lubi: A Threat to npm Packages

salabunli-nibia-lubi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165699: Malicious code in salabunli-nibia-lubi (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

salabunli-nibia-lubi is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in salabunli-nibia-lubi originates from its design to include autopublish scripts that automatically create and publish numerous derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also modifies the package.json file to remove private flags and alter version numbers. The ramifications include potential security risks for developers who inadvertently integrate these malicious packages into their projects, leading to further exploitation and degradation of the npm ecosystem.

How To Fix

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

npm uninstall salabunli-nibia-lubi

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 use the following command to prevent the installation of this malicious package in your project: 'npm install --no-optional salabunli-nibia-lubi'. However, this does not eliminate the risk associated with the package and should not be considered a permanent solution.

Conclusion

The salabunli-nibia-lubi package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for salabunli-nibia-lubi →

Share this vulnerability

FAQ

salabunli-nibia-lubi is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

This vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.

You should uninstall the salabunli-nibia-lubi package immediately and check your project for any other potentially compromised packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall salabunli-nibia-lubi

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