Malicious Code Injection in nina-lumpur19-ruro Package

nina-lumpur19-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106328: Malicious code in nina-lumpur19-ruro (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 nina-lumpur19-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms to inflate developer reputation scores through the automatic generation of derivative packages.

Vulnerability Detail

The vulnerability in the nina-lumpur19-ruro package originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names, ultimately leading to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly incorporate these malicious packages into their projects, as well as damage to 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-lumpur19-ruro

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-lumpur19-ruro package and any other packages that are part of the malicious campaign. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The nina-lumpur19-ruro package poses a significant security risk due to its association with a malicious campaign that modifies package metadata and floods the npm registry. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor their projects for vulnerabilities.

See every vulnerability recorded for nina-lumpur19-ruro →

Share this vulnerability

FAQ

The nina-lumpur19-ruro package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

Incorporating the nina-lumpur19-ruro package can lead to security risks, including the potential for your project to be polluted with malicious code and derivative packages.

If you have installed the nina-lumpur19-ruro package, you should uninstall it immediately using the command: npm uninstall nina-lumpur19-ruro.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall nina-lumpur19-ruro

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