Malicious Code Injection in nadia-lapis4-breki Package

nadia-lapis4-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74519: Malicious code in nadia-lapis4-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 nadia-lapis4-breki package is part of the npm ecosystem, often utilized in various JavaScript projects. It is typically involved in automating tasks related to package management. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation and publication of numerous derivative packages with randomized names.

Vulnerability Detail

The vulnerability in the nadia-lapis4-breki package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of projects relying on this package. The malicious code is designed to exploit the npm ecosystem, making it a significant threat to developers and users of affected packages.

How To Fix

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

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

Conclusion

The nadia-lapis4-breki package poses a significant security risk due to its malicious code that alters package management files and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package to protect their projects from potential threats.

See every vulnerability recorded for nadia-lapis4-breki →

Share this vulnerability

FAQ

The nadia-lapis4-breki package is an npm package used in JavaScript projects, but it has been identified as part of a malicious campaign.

The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.

You should immediately update or uninstall the nadia-lapis4-breki package to mitigate the risk of malicious code execution.

Yes, you can use Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software without requiring code access or installation.

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

How To Fix

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

npm uninstall nadia-lapis4-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