Malicious Code Injection in rina-kue48-breki: A Threat to npm Packages

rina-kue48-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75257: Malicious code in rina-kue48-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 rina-kue48-breki is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to a token reward campaign that has been identified as malicious. It is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names, which can inflate developer reputation scores for token rewards. This behavior poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in rina-kue48-breki stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the integrity of the packages within it. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to achieve its goals.

How To Fix

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

npm uninstall rina-kue48-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 rina-kue48-breki package altogether. If it is already included in your project, consider removing it and replacing it with a trusted alternative. Monitor your package-lock.json file for any unauthorized changes, and use tools like Vulert to keep track of vulnerabilities in your dependencies.

Conclusion

The rina-kue48-breki package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant and remove such packages from their projects. Regular monitoring and updates can help maintain the security of your software dependencies.

See every vulnerability recorded for rina-kue48-breki →

Share this vulnerability

FAQ

The rina-kue48-breki package is an npm package that has been identified as malicious, designed to manipulate the npm registry for token rewards.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity and security of your project's dependencies.

If you have installed the rina-kue48-breki package, you should uninstall it immediately using the command: npm uninstall rina-kue48-breki.

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

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

How To Fix

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

npm uninstall rina-kue48-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