Malicious Code Injection in indah-teh12-breki Package - npm Vulnerability

indah-teh12-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73503: Malicious code in indah-teh12-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 indah-teh12-breki package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages designed to inflate developer reputation scores. This package, like others in the campaign, contains scripts that automate the generation and publication of derivative packages, leading to potential security risks.

Vulnerability Detail

The vulnerability originates from the malicious design of the indah-teh12-breki package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can lead to unauthorized access, data leakage, and a compromised development environment.

How To Fix

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

npm uninstall indah-teh12-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 measure, avoid using the indah-teh12-breki package and monitor your project for any dependencies that may have been affected by this malicious package. You can also use tools like Vulert to monitor your project for vulnerabilities. To check if your application is affected, you can use the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The indah-teh12-breki package poses a significant security risk due to its malicious code that modifies package configurations and repopulates the npm registry with potentially harmful variants. It is essential to remove this package from your project and monitor for any vulnerabilities using tools like Vulert.

See every vulnerability recorded for indah-teh12-breki →

Share this vulnerability

FAQ

The indah-teh12-breki package is an npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and security.

You should uninstall the indah-teh12-breki package immediately using the command npm uninstall indah-teh12-breki.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time, using just your package-lock.json.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall indah-teh12-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