Malicious Code Detected in npm Package: nina-lupis59-ruro

nina-lupis59-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106331: Malicious code in nina-lupis59-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'nina-lupis59-ruro' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores through automated publishing scripts. They generate and publish numerous derivative packages with randomized names, which can clutter the npm registry and potentially introduce security risks.

Vulnerability Detail

The vulnerability in 'nina-lupis59-ruro' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and creates random package names. This behavior is intended to continuously republish variants, polluting the npm registry and compromising the integrity of the ecosystem. The origin of this issue is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes.

How To Fix

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

npm uninstall nina-lupis59-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 this package and monitor your dependencies for any similar malicious packages. Regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.

Conclusion

The 'nina-lupis59-ruro' package contains malicious code that poses a significant risk to the npm ecosystem. It is crucial to remove this package from your projects and monitor your dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for nina-lupis59-ruro →

Share this vulnerability

FAQ

The malicious code can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially introducing security risks to your application.

You can use Vulert to monitor your application for vulnerabilities. By analyzing your package-lock.json file, Vulert provides real-time alerts for any open-source vulnerabilities.

There is no patch for the 'nina-lupis59-ruro' package as it is recommended to uninstall it instead of updating.

You should evaluate your dependencies and find alternatives that do not rely on this malicious package. Consider reaching out to the maintainers of those dependencies for guidance.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the npm ecosystem.

How To Fix

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

npm uninstall nina-lupis59-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