Malicious Code Injection in udin-jus92-breki: A Threat to npm Ecosystem

udin-jus92-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75811: Malicious code in udin-jus92-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'udin-jus92-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in 'udin-jus92-breki' originates from its inclusion in a malicious campaign that employs scripts to alter the package.json file. This alteration removes private flags, changes version numbers, and generates random package names, which can lead to significant pollution of the npm registry. The ramifications include compromised developer reputations and potential security risks for applications relying on these packages. The package is designed to continuously republish variants, exacerbating the issue.

How To Fix

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

npm uninstall udin-jus92-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 'udin-jus92-breki' package in your project. If it is already included, remove it by running: npm uninstall udin-jus92-breki. Additionally, consider using Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without requiring any signup.

Conclusion

The 'udin-jus92-breki' package poses a significant risk due to its malicious code designed to manipulate package metadata and republish variants. It is crucial to remove this package from your projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities.

See every vulnerability recorded for udin-jus92-breki →

Share this vulnerability

FAQ

'udin-jus92-breki' is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your application and potentially introducing security risks.

You should uninstall the 'udin-jus92-breki' package immediately and monitor your project for any vulnerabilities using tools like Vulert.

Regularly monitor your dependencies for vulnerabilities and use tools like Vulert to receive real-time alerts for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without requiring any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall udin-jus92-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