Malicious Code Injection in nadia-kepok26-ruro: A Threat to npm Packages

nadia-kepok26-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106089: Malicious code in nadia-kepok26-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-kepok26-ruro is part of a broader ecosystem within npm, primarily associated with the tea.xyz token reward campaign. This package, like others in the campaign, is designed to manipulate npm's publishing system by generating and publishing derivative packages with randomized names. Its functionality is compromised due to the presence of malicious scripts that aim to inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in nadia-kepok26-ruro stems from its inclusion in a malicious campaign that employs autopublish scripts to alter package.json files. These scripts remove private flags, change version numbers, and create random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall nadia-kepok26-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 nadia-kepok26-ruro package and consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The nadia-kepok26-ruro package poses a significant threat due to its malicious code designed to exploit npm's publishing system. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for nadia-kepok26-ruro →

Share this vulnerability

FAQ

nadia-kepok26-ruro is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.

If you have installed nadia-kepok26-ruro, you should uninstall it immediately and check for any other affected packages.

You can use tools like Vulert, which allows you to monitor your project for open-source vulnerabilities by analyzing your package-lock.json file.

Yes, consider using other reputable npm packages that offer similar functionality without the associated risks.

How To Fix

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

npm uninstall nadia-kepok26-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