Malicious Code Injection in nina-buburayam26-riris: A Threat to npm Ecosystem

nina-buburayam26-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88781: Malicious code in nina-buburayam26-riris (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 'nina-buburayam26-riris' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system, often flooding the registry with numerous derivative packages. The primary functionality of these packages is to inflate developer reputation scores through automated scripts that generate and publish variants with randomized names.

Vulnerability Detail

The vulnerability in 'nina-buburayam26-riris' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry, making it difficult for developers to manage their dependencies effectively. The origin of this vulnerability is linked to the broader trend of malicious packages that exploit npm's publishing mechanisms for token rewards, posing significant risks to developers relying on 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 nina-buburayam26-riris

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 'nina-buburayam26-riris' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your project for vulnerabilities. To check if your application is affected by this vulnerability, you can use the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'nina-buburayam26-riris' package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for nina-buburayam26-riris →

Share this vulnerability

FAQ

The vulnerability can lead to the pollution of the npm registry, making it challenging for developers to manage their dependencies and potentially introducing security risks into their applications.

You can check your project's package.json file or use the command 'npm list nina-buburayam26-riris' to see if the package is included in your dependencies.

If you have installed the package, you should uninstall it immediately using 'npm uninstall nina-buburayam26-riris' and look for alternative packages.

Regularly audit your dependencies using tools like Vulert, keep your packages updated, and be cautious when adding new packages from unknown sources.

Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json.

How To Fix

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

npm uninstall nina-buburayam26-riris

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