Malicious Code Injection in rina-buburayam51-breki Package

rina-buburayam51-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75244: Malicious code in rina-buburayam51-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 Penetration testing for web, API and mobile 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-buburayam51-breki package is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package configurations and republishing behaviors.

Vulnerability Detail

The vulnerability stems from the package's malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random Indonesian-themed package names and continuously republishes variants, leading to pollution of the npm registry. This behavior can compromise the integrity of the npm ecosystem and potentially expose users to further security risks.

How To Fix

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

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

Conclusion

The rina-buburayam51-breki package has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. It is crucial to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert.

See every vulnerability recorded for rina-buburayam51-breki →

Share this vulnerability

FAQ

It is an npm package that is part of a token reward campaign and has been identified to contain malicious code.

The vulnerability can lead to unauthorized changes in your package configurations and may expose your application to further security risks.

You should uninstall the package immediately using 'npm uninstall rina-buburayam51-breki' and check for any dependencies that may be affected.

No patches are available for this specific package, and it is recommended to remove it entirely.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

How To Fix

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

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