Malicious Code Vulnerability in tearankbreak Package

tearankbreak Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98400: Malicious code in tearankbreak (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 tearankbreak package is part of a broader campaign associated with the tea.xyz token reward system, which has been flooding the npm ecosystem. This package is designed to manipulate npm's reputation system by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for rewards related to the tea protocol, but this functionality comes with significant risks due to its malicious behavior.

Vulnerability Detail

The vulnerability in the tearankbreak package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the package management system.

How To Fix

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

npm uninstall tearankbreak

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 measure, avoid using the tearankbreak package and monitor your project's dependencies for any signs of malicious activity. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file. For example, you can visit the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability without needing to sign up.

Conclusion

The tearankbreak package poses a significant threat to the npm ecosystem due to its malicious behavior, which includes modifying package files and republishing compromised packages. It is crucial for developers to be vigilant, remove such packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for tearankbreak →

Share this vulnerability

FAQ

The tearankbreak package is part of a malicious campaign that aims to inflate developer reputation scores in the npm ecosystem by generating and publishing numerous derivative packages.

The vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json file and potentially leads to security breaches.

You should uninstall the tearankbreak package immediately using the command npm uninstall tearankbreak and review your project's dependencies for any other potential vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without signing up.

There are no patches available for the tearankbreak package due to its malicious nature. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall tearankbreak

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