Malicious Code Injection in ida-bakso91-breki Package

ida-bakso91-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73420: Malicious code in ida-bakso91-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 ida-bakso91-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the ida-bakso91-breki package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, primarily themed around Indonesian culture. The continuous republishing of these variants can lead to a polluted npm registry, making it difficult for developers to find legitimate packages and potentially compromising the security of applications that depend on these packages.

How To Fix

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

npm uninstall ida-bakso91-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 ida-bakso91-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project 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 ida-bakso91-breki package poses a significant risk due to its malicious code that modifies package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain application security.

See every vulnerability recorded for ida-bakso91-breki →

Share this vulnerability

FAQ

The ida-bakso91-breki package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially compromising the security of applications that depend on these packages.

You should uninstall the ida-bakso91-breki package immediately using 'npm uninstall ida-bakso91-breki' and check for any alternative packages.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can also check for vulnerabilities using the Vulert playground.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and avoid using packages that are not well-maintained or have been flagged for malicious activity.

How To Fix

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

npm uninstall ida-bakso91-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