Malicious Code Injection in nana-mieaceh43-ruro Package - npm Vulnerability

nana-mieaceh43-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106164: Malicious code in nana-mieaceh43-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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The nana-mieaceh43-ruro package is part of the npm ecosystem, often utilized for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the nana-mieaceh43-ruro package stems from its malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for dependency confusion and the introduction of untrusted code into applications.

How To Fix

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

npm uninstall nana-mieaceh43-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 nana-mieaceh43-ruro package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.

Conclusion

The nana-mieaceh43-ruro package poses a significant security risk due to its malicious code that modifies package metadata and repackages itself under random names. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain application security.

See every vulnerability recorded for nana-mieaceh43-ruro →

Share this vulnerability

FAQ

The nana-mieaceh43-ruro package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can introduce untrusted code into your application, potentially leading to security breaches and dependency confusion.

You should uninstall the nana-mieaceh43-ruro package immediately and look for secure alternatives to replace its functionality.

Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities without needing to access the code or install additional software.

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-mieaceh43-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