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

laila-mie29-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74072: Malicious code in laila-mie29-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The laila-mie29-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 token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the laila-mie29-breki package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall laila-mie29-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-mie29-breki package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The laila-mie29-breki package has been identified as containing malicious code that poses significant risks to developers and their applications. It is essential to remove this package and monitor your dependencies to maintain the security of your projects.

See every vulnerability recorded for laila-mie29-breki →

Share this vulnerability

FAQ

laila-mie29-breki is an npm package that is part of a token reward campaign, designed to generate and publish derivative packages automatically.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should immediately uninstall the laila-mie29-breki package using 'npm uninstall laila-mie29-breki' and review your project's dependencies for any other potentially harmful packages.

Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using the Vulert playground without needing to sign up.

Regularly update your dependencies, use trusted packages, and utilize tools like Vulert to monitor for vulnerabilities in your project.

How To Fix

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

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