Malicious Code Injection in nina-dradag13-breki: A Threat to npm Users

nina-dradag13-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74589: Malicious code in nina-dradag13-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 'nina-dradag13-breki' is part of the npm ecosystem and has been identified as a malicious package linked to 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 for token rewards. Its functionality is primarily centered around automating the publication of these malicious packages, posing a significant risk to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'nina-dradag13-breki' originates from its malicious intent to modify the package.json file 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 a compromised development environment, loss of trust in the npm ecosystem, and potential exploitation of developers who unknowingly use these packages.

How To Fix

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

npm uninstall nina-dradag13-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 avoid using the 'nina-dradag13-breki' package altogether. If you have dependencies that require it, consider looking for alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'nina-dradag13-breki' package poses a significant threat to npm users due to its malicious behavior of modifying package files and publishing harmful variants. It is essential to remove this package and monitor your project for any vulnerabilities using tools like Vulert to ensure a secure development environment.

See every vulnerability recorded for nina-dradag13-breki →

Share this vulnerability

FAQ

The main risk is that it modifies your package.json file and publishes malicious variants, which can compromise your development environment and the integrity of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without needing to sign up.

You should immediately uninstall the package using 'npm uninstall nina-dradag13-breki' and check your project for any other potentially malicious packages.

Yes, consider searching for other reputable npm packages that provide similar functionality without the associated risks of malicious behavior.

Vulert uses your package-lock.json file to monitor and alert you in real-time about open-source vulnerabilities, helping you maintain a secure development environment.

How To Fix

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

npm uninstall nina-dradag13-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