Malicious Code Injection in udin-rojak92-breki Package - npm Vulnerability

udin-rojak92-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75830: Malicious code in udin-rojak92-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 udin-rojak92-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, potentially compromising the integrity of applications that depend on it.

Vulnerability Detail

The vulnerability in the udin-rojak92-breki package originates from its involvement in a token reward campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and inflate developer reputation scores fraudulently. The ramifications include potential security risks for applications that inadvertently depend on these malicious packages, as they may introduce unwanted code or vulnerabilities.

How To Fix

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

npm uninstall udin-rojak92-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 udin-rojak92-breki package and replace it with a trusted alternative. Always review the dependencies in your package.json file and ensure they are from reputable sources.

Conclusion

The udin-rojak92-breki package poses a significant risk due to its malicious code injection capabilities. It is essential for developers to be vigilant about their dependencies and take proactive measures to remove any compromised packages. Regular monitoring and updates can help maintain the security of applications.

See every vulnerability recorded for udin-rojak92-breki →

Share this vulnerability

FAQ

The udin-rojak92-breki package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

If your application depends on the udin-rojak92-breki package, it may be exposed to malicious code that can compromise security and stability.

You should uninstall the udin-rojak92-breki package immediately using the command npm uninstall udin-rojak92-breki and review your other dependencies for potential vulnerabilities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities 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 udin-rojak92-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