Malicious Code Vulnerability in nadia-gandul70-breki Package

nadia-gandul70-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74506: Malicious code in nadia-gandul70-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The nadia-gandul70-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package metadata and republishes variants to pollute the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious payload embedded within the nadia-gandul70-breki package. This payload alters the package.json file by removing private flags, changing version numbers, and generating random package names, which can lead to the proliferation of unwanted packages in the npm registry. The continuous republishing of these variants can compromise the integrity of the npm ecosystem and affect developers relying on legitimate packages.

How To Fix

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

npm uninstall nadia-gandul70-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 workaround, you can monitor your dependencies using tools like Vulert, which allows you to check for vulnerabilities in your package-lock.json file without requiring code access or installation. You can use the Vulert playground at https://vulert.com/scanner to verify if your application is affected by this vulnerability.

Conclusion

The nadia-gandul70-breki package contains malicious code that poses a significant risk to the npm ecosystem. It is crucial to uninstall this package and monitor your dependencies to maintain the integrity of your projects.

See every vulnerability recorded for nadia-gandul70-breki →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file and can lead to the creation of unwanted packages, polluting the npm registry.

You should uninstall the nadia-gandul70-breki package immediately using 'npm uninstall nadia-gandul70-breki'.

Yes, regularly monitor your dependencies using tools like Vulert to detect vulnerabilities early.

There is no patch for this specific package; the recommended action is to uninstall it.

How To Fix

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

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