Malicious Code Injection in tania-kacang22-breki: A Threat to npm Users

tania-kacang22-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75573: Malicious code in tania-kacang22-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-kacang22-breki is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish numerous variants to inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in tania-kacang22-breki originates from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This behavior not only compromises the security of applications relying on this package but also undermines the trustworthiness of the npm ecosystem as a whole. The package is designed to automatically republish variants, making it difficult to track and mitigate the issue.

How To Fix

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

npm uninstall tania-kacang22-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, avoid using the tania-kacang22-breki package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The tania-kacang22-breki package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. Users are advised to uninstall the package immediately and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for tania-kacang22-breki →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package metadata and floods the npm registry with derivative packages.

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

Immediately uninstall the package using npm uninstall tania-kacang22-breki and review your project's dependencies for any other vulnerabilities.

Yes, consider looking for other npm packages that provide similar functionality without the associated risks. Always check the package's reputation and reviews before installation.

Regularly audit your dependencies using tools like npm audit, and stay informed about vulnerabilities reported in the npm ecosystem.

How To Fix

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

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