Malicious Code Injection in irma-lumpur10-breki: A Threat to npm Ecosystem

irma-lumpur10-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73529: Malicious code in irma-lumpur10-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 'irma-lumpur10-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with a token reward campaign that has been known to flood the npm registry with malicious packages. Its primary function is to facilitate the distribution of software, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in 'irma-lumpur10-breki' originates 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 is intended to inflate developer reputation scores through the automatic generation and republishing of derivative packages, ultimately polluting the npm registry. The malicious payload can lead to security risks for developers and users who unknowingly install these compromised packages.

How To Fix

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

npm uninstall irma-lumpur10-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 'irma-lumpur10-breki' package until a secure version is released. Additionally, consider using tools like Vulert to monitor your package-lock.json file 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 'irma-lumpur10-breki' package has been identified as containing malicious code that poses a significant risk to users and developers within the npm ecosystem. It is crucial to stay informed about such vulnerabilities and take proactive measures to secure your applications.

See every vulnerability recorded for irma-lumpur10-breki →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package metadata to inflate developer reputation scores and republish compromised packages.

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

If you have installed the package, it is recommended to update it to the latest version or remove it from your project until a secure version is available.

Yes, the vulnerability can lead to security risks, including the installation of compromised packages that may harm your application or data.

Vulert is a tool that monitors your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues without requiring code access or installation.

How To Fix

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

npm uninstall irma-lumpur10-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