Malicious Code Injection in rina-martabak19-breki: npm Package Vulnerability

rina-martabak19-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75265: Malicious code in rina-martabak19-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-martabak19-breki package is part of the npm ecosystem, often utilized for various JavaScript applications. It is designed to facilitate the development and management of JavaScript projects. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts, compromising the integrity of the software supply chain.

Vulnerability Detail

This vulnerability originates from the rina-martabak19-breki package, which is linked to a broader malicious activity involving the tea.xyz token reward campaign. The package contains scripts that automatically modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior leads to the pollution of the npm registry, potentially affecting developers' reputations and the security of applications relying on these packages.

How To Fix

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

npm uninstall rina-martabak19-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-martabak19-breki package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The rina-martabak19-breki package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your dependencies to maintain the security of your applications.

See every vulnerability recorded for rina-martabak19-breki →

Share this vulnerability

FAQ

The rina-martabak19-breki package is an npm package used in JavaScript applications, but it has been identified as malicious due to its involvement in a campaign that floods the npm registry.

This vulnerability can compromise the integrity of your application by introducing malicious code that modifies your package.json file and potentially affects your application's behavior.

If you have installed the rina-martabak19-breki package, you should uninstall it immediately and audit your project for any other potentially harmful dependencies.

There are no patches available for the rina-martabak19-breki package as it is inherently malicious. The best course of action is to remove it from your project.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application using the Vulert playground without any signup.

How To Fix

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

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