Malicious Code Injection in tania-wajit24-breki Package

tania-wajit24-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75614: Malicious code in tania-wajit24-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 tania-wajit24-breki package is part of the npm ecosystem, often used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that can inflate developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, making it vulnerable to exploitation.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the tania-wajit24-breki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The malicious payload can result in unauthorized access to sensitive information and can compromise the integrity of the npm ecosystem by flooding it with unwanted packages.

How To Fix

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

npm uninstall tania-wajit24-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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include this package by checking your package.json and removing any references to it.

Conclusion

The tania-wajit24-breki package contains malicious code that poses a significant risk to projects using it. It is crucial to remove this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for tania-wajit24-breki →

Share this vulnerability

FAQ

The tania-wajit24-breki package is part of a campaign that aims to inflate developer reputation scores through the automatic generation of derivative npm packages.

The malicious code can modify your package.json file, remove private flags, and generate unwanted package names, potentially compromising your project's integrity.

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

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability 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-wajit24-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