Malicious Code Injection in tiara-mieayam18-breki Package

tiara-mieayam18-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75644: Malicious code in tiara-mieayam18-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 tiara-mieayam18-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like many others in the campaign, is designed to inflate developer reputation scores by generating and publishing derivative packages with randomized names. Its functionality is compromised due to the presence of malicious code that modifies package metadata.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the tiara-mieayam18-breki package. This payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. It continuously republishes these variants to pollute the npm registry, which can lead to security risks for developers who unknowingly use these compromised packages. The malicious behavior is primarily aimed at exploiting the npm ecosystem for token rewards.

How To Fix

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

npm uninstall tiara-mieayam18-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 tiara-mieayam18-breki package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your dependencies for vulnerabilities. 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 tiara-mieayam18-breki package poses a significant risk due to its malicious code that alters package metadata and repackages itself. It is crucial to remove this package from your projects and monitor your dependencies for similar vulnerabilities using tools like Vulert.

See every vulnerability recorded for tiara-mieayam18-breki →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores.

The malicious code modifies your package.json, removes private flags, and repackages your project with potentially harmful variants, leading to security vulnerabilities.

You should uninstall the package immediately and check your package-lock.json for any references to it, removing them as necessary.

Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall tiara-mieayam18-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