Malicious Code Injection in lutfi-enting73-breki Package

lutfi-enting73-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74224: Malicious code in lutfi-enting73-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The lutfi-enting73-breki package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the lutfi-enting73-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 issue is linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores by polluting the npm registry with numerous derivative packages. The ramifications include potential security risks for developers who unknowingly install these malicious packages, as they can compromise the integrity of their applications.

How To Fix

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

npm uninstall lutfi-enting73-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 remove the lutfi-enting73-breki package from your project by executing the following command: npm uninstall lutfi-enting73-breki. This will prevent any malicious code from executing in your environment until a secure version is available.

Conclusion

The lutfi-enting73-breki package contains a significant vulnerability due to its malicious code that alters package configurations and floods the npm registry with derivative packages. It is crucial for developers to update or remove this package to safeguard their applications from potential security threats.

See every vulnerability recorded for lutfi-enting73-breki →

Share this vulnerability

FAQ

The lutfi-enting73-breki package is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores.

The vulnerability can compromise the integrity of your application by introducing malicious code that modifies package configurations and republishing variants to the npm registry.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. You can check your application by using the Vulert playground at Vulert Scanner without any signup.

If you cannot update the package, consider removing it from your project as a temporary measure to avoid potential security risks.

More information can be found on the GitHub repository for malicious packages or by consulting the npm registry for updates regarding the lutfi-enting73-breki package.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall lutfi-enting73-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