Malicious Code Injection in lisa-dradag54-breki: A Threat to npm Ecosystem

lisa-dradag54-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74163: Malicious code in lisa-dradag54-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 package 'lisa-dradag54-breki' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious behavior of this package compromises the integrity of the npm registry and poses a significant risk to developers relying on npm for package management.

Vulnerability Detail

The vulnerability in 'lisa-dradag54-breki' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry, making it difficult for developers to trust the packages they use. The origin of this vulnerability is linked to the automated scripts (auto.js, autopublish.js, etc.) that are embedded within these malicious packages, which are designed to exploit the npm ecosystem.

How To Fix

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

npm uninstall lisa-dradag54-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 'lisa-dradag54-breki' package and replace it with a known, secure alternative. Always verify the integrity and source of packages before installation.

Conclusion

The 'lisa-dradag54-breki' package represents a significant threat within the npm ecosystem due to its malicious behavior. Developers must take proactive steps to remove such packages and utilize tools like Vulert to monitor for vulnerabilities in their projects. By staying informed and vigilant, the risks associated with malicious packages can be mitigated.

See every vulnerability recorded for lisa-dradag54-breki →

Share this vulnerability

FAQ

The impact includes potential exposure to malicious code that can compromise your project and the integrity of the npm registry.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.

Immediately uninstall the package and review your project for any unintended consequences caused by its use.

There are no patches available for 'lisa-dradag54-breki' as it is a malicious package. The best course of action is to remove it entirely.

Regularly audit your dependencies, use trusted sources, and consider using tools like Vulert for real-time monitoring of vulnerabilities.

How To Fix

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

npm uninstall lisa-dradag54-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