Malicious Code Injection in indah-klanting69-breki Package

indah-klanting69-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73480: Malicious code in indah-klanting69-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 Penetration testing for web, API and mobile 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-klanting69-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the indah-klanting69-breki package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. The ramifications include pollution of the npm registry and potential exploitation of developers' reputation scores, making it a significant threat to the integrity of the ecosystem.

How To Fix

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

npm uninstall indah-klanting69-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, you can avoid using the indah-klanting69-breki package and monitor your project for any dependencies that may inadvertently include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The indah-klanting69-breki package poses a significant threat due to its malicious code that alters package metadata and inflates reputation scores. Immediate action is required to remove the package and monitor for any further vulnerabilities. Utilizing tools like Vulert can enhance your project's security posture.

See every vulnerability recorded for indah-klanting69-breki →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json, removes private flags, and generates random package names, which can lead to reputation score inflation and registry pollution.

You should uninstall the package immediately using 'npm uninstall indah-klanting69-breki' and monitor your dependencies for any related vulnerabilities.

Regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without any signup.

How To Fix

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

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