Malicious Code Injection in iwan-rujak41-breki Package - npm Vulnerability

iwan-rujak41-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73597: Malicious code in iwan-rujak41-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 iwan-rujak41-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 its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the iwan-rujak41-breki package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation by attackers. The origin of this vulnerability is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting developers involved in token reward campaigns.

How To Fix

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

npm uninstall iwan-rujak41-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 measure, you can avoid using the iwan-rujak41-breki package and monitor your dependencies for any similar malicious packages. Regularly audit your npm packages using the command: npm audit to identify vulnerabilities.

Conclusion

The iwan-rujak41-breki package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to remove this package and regularly audit your dependencies to maintain the security of your applications.

See every vulnerability recorded for iwan-rujak41-breki →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automatically generate and publish derivative packages.

The malicious code modifies your package.json file, potentially exposing your application to security risks and polluting the npm registry.

You should uninstall the package immediately using the command: npm uninstall iwan-rujak41-breki.

Regularly audit your dependencies, use trusted packages, and stay informed about known vulnerabilities in the npm ecosystem.

Yes, Vulert can monitor your package-lock.json for open-source vulnerabilities in real-time, alerting you to any issues without requiring code access.

How To Fix

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

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