Malicious Code Injection in laila-bubur78-breki Package - npm Vulnerability

laila-bubur78-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74046: Malicious code in laila-bubur78-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 laila-bubur78-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. However, it has been identified as containing malicious code that modifies package configurations and publishes harmful variants to the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the laila-bubur78-breki package, which is part of a larger scheme to manipulate npm's package registry. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This can lead to the pollution of the npm registry and potentially compromise the integrity of applications relying on these packages.

How To Fix

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

npm uninstall laila-bubur78-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 laila-bubur78-breki package and any other packages that may be associated with the tea.xyz token reward campaign. Regularly audit your dependencies to ensure that no malicious packages are included.

Conclusion

The laila-bubur78-breki package poses a significant risk due to its malicious code that alters package configurations and publishes harmful variants. It is crucial to remove this package from your project and monitor your dependencies for any vulnerabilities to ensure the security of your applications.

See every vulnerability recorded for laila-bubur78-breki →

Share this vulnerability

FAQ

It is an npm package that is part of a token reward campaign and has been identified to contain malicious code.

The malicious code can modify your package configurations and lead to the publication of harmful variants, potentially compromising your application.

You should uninstall the laila-bubur78-breki package immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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