Malicious Code Injection in rina-serimuka94-breki Package: A Threat to npm Users

rina-serimuka94-breki Updated 23 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75292: Malicious code in rina-serimuka94-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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The rina-serimuka94-breki package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the rina-serimuka94-breki package originates from its association with the tea.xyz token reward campaign. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This malicious behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall rina-serimuka94-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 malicious package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include the rina-serimuka94-breki package and regularly audit your dependencies for any malicious code.

Conclusion

The rina-serimuka94-breki package poses a significant threat to npm users due to its malicious code designed to exploit the npm registry. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for rina-serimuka94-breki →

Share this vulnerability

FAQ

The rina-serimuka94-breki package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

This vulnerability can compromise the integrity of your project by introducing malicious code that alters your package.json file and potentially leads to security breaches.

If you have installed the rina-serimuka94-breki package, you should uninstall it immediately using 'npm uninstall rina-serimuka94-breki' and audit your project for any other malicious dependencies.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities 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-serimuka94-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