Malicious Code Injection in tiara-tomat97-breki: A Threat to npm Users

tiara-tomat97-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75677: Malicious code in tiara-tomat97-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package tiara-tomat97-breki is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system, often containing scripts that automatically generate and publish derivative packages. This behavior is intended to inflate developer reputation scores for token rewards, making the package a potential vector for malicious activity.

Vulnerability Detail

The vulnerability in tiara-tomat97-breki arises from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting developers engaged in token reward campaigns.

How To Fix

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

npm uninstall tiara-tomat97-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 the vulnerable package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include tiara-tomat97-breki or any of its derivatives. You can also use the following command to uninstall the package: npm uninstall tiara-tomat97-breki.

Conclusion

The tiara-tomat97-breki package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to stay vigilant, update their packages, and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for tiara-tomat97-breki →

Share this vulnerability

FAQ

tiara-tomat97-breki is an npm package that is part of a malicious campaign aimed at manipulating the npm registry for token rewards.

The vulnerability can lead to the pollution of your project's dependencies, potentially introducing malicious code that compromises security and functionality.

If you have installed tiara-tomat97-breki, you should uninstall it immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

Yes, 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 tiara-tomat97-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