Malicious Code Injection in nana-kue7-ruro Package

nana-kue7-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106155: Malicious code in nana-kue7-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 nana-kue7-ruro package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to reputation inflation for malicious actors. The vulnerability stems from its ability to modify critical files like package.json, making it a significant risk for developers using this package.

Vulnerability Detail

The vulnerability in the nana-kue7-ruro package originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically publish variants of itself with altered package names and modified metadata. This behavior can lead to the pollution of the npm registry, making it difficult for developers to trust the integrity of packages. The malicious payload specifically removes private flags from package.json and changes version numbers, which can result in unintended exposure of sensitive information and compromise the security of applications relying on this package.

How To Fix

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

npm uninstall nana-kue7-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 measure, avoid using the nana-kue7-ruro package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package-lock.json file to identify any potentially vulnerable packages.

Conclusion

The nana-kue7-ruro package poses a significant risk due to its malicious behavior, which can compromise the integrity of applications relying on it. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your projects.

See every vulnerability recorded for nana-kue7-ruro →

Share this vulnerability

FAQ

The nana-kue7-ruro package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the pollution of the npm registry, making it difficult to trust the integrity of packages, and may expose sensitive information.

You should uninstall the nana-kue7-ruro package immediately and audit your dependencies for any other potentially malicious packages.

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

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

How To Fix

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

npm uninstall nana-kue7-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