Malicious Code Injection in rina-nasi58-breki Package

rina-nasi58-breki Updated 23 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75274: Malicious code in rina-nasi58-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 rina-nasi58-breki package is part of the npm ecosystem, typically used for various JavaScript applications. It has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automated generation and publication of derivative packages. This package, like others in the campaign, is designed to manipulate the npm registry by creating numerous variants of itself with altered names and metadata.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names, leading to potential pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may introduce security risks into their applications.

How To Fix

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

npm uninstall rina-nasi58-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 workaround, you can avoid using the rina-nasi58-breki package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The rina-nasi58-breki package poses a significant risk due to its malicious nature, which can compromise the integrity of applications using it. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain secure software practices.

See every vulnerability recorded for rina-nasi58-breki →

Share this vulnerability

FAQ

The rina-nasi58-breki package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

This vulnerability can lead to the inclusion of compromised packages in your application, potentially introducing security risks and instability.

You should remove the rina-nasi58-breki package from your project and monitor for any updates or patches that may be released.

Yes, Vulert allows you to monitor and alert in real-time for open-source vulnerabilities using your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground.

Regularly audit your dependencies using tools like npm audit, and stay informed about vulnerabilities in the packages you use.

How To Fix

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

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