Malicious Code Injection in nadia-donat96-ruro Package

nadia-donat96-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106083: Malicious code in nadia-donat96-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The nadia-donat96-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to manipulate npm's registry by creating and publishing numerous derivative packages. The primary functionality of this package is to facilitate token reward campaigns, but it has been compromised to execute harmful scripts.

Vulnerability Detail

The nadia-donat96-ruro package contains malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior 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-donat96-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 nadia-donat96-ruro package and replace it with a trusted alternative. Additionally, you can use tools like Vulert to monitor your package-lock.json for vulnerabilities. To check if your application is affected by this vulnerability, you can visit the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The nadia-donat96-ruro package has been compromised to include malicious code that affects the npm ecosystem. It is crucial for developers to be vigilant, regularly check their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action is required to uninstall the affected package and safeguard your applications.

See every vulnerability recorded for nadia-donat96-ruro →

Share this vulnerability

FAQ

The nadia-donat96-ruro package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

If you have installed the nadia-donat96-ruro package, you should uninstall it immediately using 'npm uninstall nadia-donat96-ruro' and check your project for any other compromised packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time, helping you stay informed about potential risks.

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

How To Fix

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

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