Malicious Code Injection in tania-kue90-breki: A Threat to npm Packages

tania-kue90-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75580: Malicious code in tania-kue90-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 package tania-kue90-breki 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 exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in tania-kue90-breki stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to pollute the npm registry with numerous variants of the package, which can lead to confusion among developers and potential security risks if these packages are inadvertently used in projects. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with various malicious npm packages.

How To Fix

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

npm uninstall tania-kue90-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 tania-kue90-breki package and any packages that depend on it. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The tania-kue90-breki package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for tania-kue90-breki →

Share this vulnerability

FAQ

tania-kue90-breki is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the inclusion of malicious code in your project, which may compromise security and functionality.

You should uninstall the package immediately using the command npm uninstall tania-kue90-breki.

Regularly update your dependencies, monitor your package-lock.json with tools like Vulert, and be cautious when adding new packages.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall tania-kue90-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