Malicious Code Injection in rina-sego26-breki: A Threat to npm Ecosystem

rina-sego26-breki Updated 23 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75287: Malicious code in rina-sego26-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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The rina-sego26-breki package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality has been compromised, making it a vector for malicious code that can affect users and developers alike.

Vulnerability Detail

The vulnerability in rina-sego26-breki originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically generate and publish derivative packages with randomized names, which can pollute the npm registry. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and continuously republishing variants. This can lead to a compromised npm ecosystem, where developers may unknowingly use malicious packages, resulting in potential security breaches and loss of trust in the npm registry.

How To Fix

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

npm uninstall rina-sego26-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 remove the rina-sego26-breki package from your project by running the command: 'npm uninstall rina-sego26-breki'. This will prevent any malicious code from executing until a patched version is available.

Conclusion

The rina-sego26-breki package poses a significant risk due to its malicious code that can compromise the npm ecosystem. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications. Regularly updating packages and using monitoring tools like Vulert can help mitigate these risks.

See every vulnerability recorded for rina-sego26-breki →

Share this vulnerability

FAQ

The rina-sego26-breki package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.

This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

If you have installed the rina-sego26-breki package, it is recommended to uninstall it immediately and monitor your application for any unusual behavior.

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-sego26-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