Malicious Code Injection in jaja-rangi86-breki: A Threat to npm Packages

jaja-rangi86-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73656: Malicious code in jaja-rangi86-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 package jaja-rangi86-breki 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. Its functionality is compromised by malicious scripts that alter package metadata and republish variants, leading to potential abuse in the npm registry.

Vulnerability Detail

The vulnerability in jaja-rangi86-breki originates from its association with 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 behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to security breaches and loss of trust in the ecosystem.

How To Fix

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

npm uninstall jaja-rangi86-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 prevent the installation of this package by using npm's package-lock.json to monitor and restrict the use of vulnerable packages. You can also use the following command to uninstall the package: npm uninstall jaja-rangi86-breki.

Conclusion

The jaja-rangi86-breki package poses a significant risk due to its malicious behavior of altering package metadata and flooding the npm registry. It is crucial for developers to be vigilant and take immediate action to remove this package and monitor their dependencies for vulnerabilities.

See every vulnerability recorded for jaja-rangi86-breki →

Share this vulnerability

FAQ

jaja-rangi86-breki is an npm package associated with a token reward campaign that has been identified as malicious due to its behavior of modifying package metadata and republishing variants.

This vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.

You should immediately uninstall the jaja-rangi86-breki package and check for any other compromised packages in your project.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall jaja-rangi86-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