Malicious Code Injection in lutfi-gado-gado71-breki Package

lutfi-gado-gado71-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74226: Malicious code in lutfi-gado-gado71-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 lutfi-gado-gado71-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the generation and publication of derivative packages with randomized names. This package, like others in the campaign, aims to inflate developer reputation scores for token rewards, making it susceptible to malicious exploitation.

Vulnerability Detail

The vulnerability in the lutfi-gado-gado71-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, which leads to the continuous republishing of variants. The origin of this vulnerability is linked to a broader trend of malicious packages flooding the npm registry, specifically targeting the tea protocol token rewards. The ramifications include pollution of the npm registry and potential security risks for developers using these packages.

How To Fix

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

npm uninstall lutfi-gado-gado71-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 workaround, you can monitor your package dependencies using tools like Vulert. Vulert allows you to check for vulnerabilities in your package-lock.json file without requiring access to the code or installation. You can use the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.

Conclusion

The lutfi-gado-gado71-breki package contains malicious code that poses a significant risk to developers using it. Immediate action is required to uninstall the package and monitor for vulnerabilities in your dependencies. Utilizing tools like Vulert can help ensure your application remains secure.

See every vulnerability recorded for lutfi-gado-gado71-breki →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, removing private flags and altering version numbers, which can lead to security risks.

You should uninstall the lutfi-gado-gado71-breki package immediately to mitigate any risks associated with its malicious code.

Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing to access the code.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability.

How To Fix

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

npm uninstall lutfi-gado-gado71-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