Malicious Code Injection in tania-botok57-breki: A Threat to npm Ecosystem

tania-botok57-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75564: Malicious code in tania-botok57-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 Your last release was probably never penetration tested 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 tania-botok57-breki is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files, such as package.json, which can lead to significant security risks for developers and users relying on npm packages.

Vulnerability Detail

The vulnerability originates from the package's malicious code, which is designed to remove private flags from package.json, alter version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional package usage by developers, potentially leading to further exploitation or security breaches. The continuous republishing of these variants can overwhelm the npm ecosystem, making it difficult for developers to identify legitimate packages.

How To Fix

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

npm uninstall tania-botok57-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 an immediate workaround, you can manually remove the package from your project by executing the following command: npm uninstall tania-botok57-breki. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities without requiring code access or installation.

Conclusion

The tania-botok57-breki package represents a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for tania-botok57-breki →

Share this vulnerability

FAQ

tania-botok57-breki is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to the unintentional use of malicious packages, potentially compromising your project's security and integrity.

You should uninstall the package immediately and monitor your project for any other vulnerabilities using tools like Vulert.

Yes, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories.

You can use the Vulert playground at Vulert Scanner to check your application 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-botok57-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