Malicious Code Injection in irma-nasipecel69-breki Package

irma-nasipecel69-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73538: Malicious code in irma-nasipecel69-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The irma-nasipecel69-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the irma-nasipecel69-breki package arises from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry by continuously republishing variants, leading to potential security risks for developers who may unknowingly use these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages.

How To Fix

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

npm uninstall irma-nasipecel69-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-nasipecel69-breki package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package-lock.json file for any malicious dependencies.

Conclusion

The irma-nasipecel69-breki package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities.

See every vulnerability recorded for irma-nasipecel69-breki →

Share this vulnerability

FAQ

The irma-nasipecel69-breki package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

This vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json and floods the npm registry with unwanted packages.

If you have installed the irma-nasipecel69-breki package, you should uninstall it immediately using the command: npm uninstall irma-nasipecel69-breki.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without needing to sign up.

How To Fix

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

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