Malicious Code Injection in irma-rujak57-breki: A Threat to npm Packages

irma-rujak57-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73544: Malicious code in irma-rujak57-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 Your last release was probably never penetration tested 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-rujak57-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised by malicious scripts that alter its metadata and continuously republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'irma-rujak57-breki' originates from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This not only compromises the integrity of the package but also poses a risk to developers who may unknowingly use these tainted packages, leading to potential security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall irma-rujak57-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, avoid using the 'irma-rujak57-breki' package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The 'irma-rujak57-breki' package is compromised by malicious code that threatens the integrity of the npm ecosystem. It is essential to remove this package from your projects and adopt best practices for dependency management to safeguard against such vulnerabilities.

See every vulnerability recorded for irma-rujak57-breki →

Share this vulnerability

FAQ

The package contains malicious code that modifies its metadata and floods the npm registry with derivative packages, compromising the integrity of the ecosystem.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Immediately uninstall the package using 'npm uninstall irma-rujak57-breki' and review your project's dependencies for any other potentially malicious packages.

Yes, consider using well-established and trusted packages that offer similar functionality. Always check the package's reputation and reviews before installation.

Regularly audit your dependencies, use tools like Vulert for monitoring, and ensure you only install packages from reputable sources.

How To Fix

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

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