Malicious Code Injection in nadia-taiwan41-ruro: A Threat to npm Ecosystem

nadia-taiwan41-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106123: Malicious code in nadia-taiwan41-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 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 nadia-taiwan41-ruro is part of the npm ecosystem and has been identified as a malicious package associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, which can inflate developer reputation scores. Its primary function is to automate the publication process, but it has been compromised to include harmful scripts.

Vulnerability Detail

The vulnerability in nadia-taiwan41-ruro originates from its malicious intent to modify package.json files by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant ramifications, including the compromise of developer accounts, loss of trust in the npm ecosystem, and potential exploitation of affected applications.

How To Fix

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

npm uninstall nadia-taiwan41-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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include nadia-taiwan41-ruro in its dependencies. You can also use tools like Vulert to monitor your project for vulnerabilities without needing to access the code directly.

Conclusion

The nadia-taiwan41-ruro package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant and take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for nadia-taiwan41-ruro →

Share this vulnerability

FAQ

nadia-taiwan41-ruro is an npm package that has been identified as malicious, designed to manipulate the npm registry and inflate developer reputation scores.

This vulnerability can compromise your project's integrity by introducing malicious code, which may lead to unauthorized access or exploitation of your application.

You should immediately uninstall the package using 'npm uninstall nadia-taiwan41-ruro' and check your project for any other vulnerabilities.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.

Yes, 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 nadia-taiwan41-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