Malicious Code Injection in laila-rangginang95-breki Package

laila-rangginang95-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74087: Malicious code in laila-rangginang95-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 laila-rangginang95-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 are often used to inflate developer reputation scores in exchange for token rewards. The package's functionality includes creating random package names and modifying existing package metadata.

Vulnerability Detail

The vulnerability in the laila-rangginang95-breki package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to flood the npm registry with similar malicious packages. The ramifications include potential pollution of the npm registry and exploitation of developer reputation systems.

How To Fix

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

npm uninstall laila-rangginang95-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 laila-rangginang95-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The laila-rangginang95-breki package contains malicious code that poses a significant risk to developers and their projects. It is crucial to remove this package and monitor your dependencies for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for laila-rangginang95-breki →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The vulnerability can lead to unauthorized modifications in your package.json file and pollution of the npm registry, potentially compromising your project's integrity.

You should uninstall the package immediately using npm uninstall laila-rangginang95-breki and check for any other affected dependencies.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.

How To Fix

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

npm uninstall laila-rangginang95-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