Malicious Code Injection in nadia-rawon26-breki: A Threat to npm Ecosystem

nadia-rawon26-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74530: Malicious code in nadia-rawon26-breki (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 package nadia-rawon26-breki is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in nadia-rawon26-breki originates from its association with a malicious campaign that employs autopublish scripts to modify package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include compromised package integrity, potential security risks for users, and a degraded npm ecosystem.

How To Fix

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

npm uninstall nadia-rawon26-breki

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-rawon26-breki package and replace it with a trusted alternative. Always verify the integrity of packages before installation.

Conclusion

The nadia-rawon26-breki package poses a significant threat due to its malicious code that manipulates package metadata. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the integrity of their applications and the npm ecosystem.

See every vulnerability recorded for nadia-rawon26-breki →

Share this vulnerability

FAQ

nadia-rawon26-breki is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata.

The vulnerability can lead to compromised package integrity, exposing your application to potential security risks and affecting its functionality.

If you have installed nadia-rawon26-breki, you should uninstall it immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.

Yes, consider using well-established and trusted packages that serve the same purpose but do not have a history of malicious activity.

How To Fix

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

npm uninstall nadia-rawon26-breki

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