Malicious Code Injection in iwan-lapis82-breki Package: A Threat to npm Users

iwan-lapis82-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73577: Malicious code in iwan-lapis82-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 iwan-lapis82-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit developers by flooding the npm registry with derivative packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, ultimately compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the iwan-lapis82-breki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. The primary risk associated with this vulnerability is the potential for developers to unknowingly install compromised packages, leading to further exploitation and pollution of the npm registry.

How To Fix

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

npm uninstall iwan-lapis82-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 iwan-lapis82-breki package and any other packages that may be part of the malicious campaign. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The iwan-lapis82-breki package poses a significant threat to npm users due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is essential to remove this package and monitor your dependencies to maintain the security of your projects.

See every vulnerability recorded for iwan-lapis82-breki →

Share this vulnerability

FAQ

The iwan-lapis82-breki package is an npm package that has been identified as part of a malicious campaign aimed at exploiting developers through automated publishing.

If you have the iwan-lapis82-breki package installed, your project may be at risk of using compromised code, which could lead to security breaches and instability.

You should remove the iwan-lapis82-breki package from your project and monitor for any updates or patches that may be released.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the npm ecosystem.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall iwan-lapis82-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