Malicious Code Injection in riana-oblok9-breki: A Threat to npm Ecosystem

riana-oblok9-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75158: Malicious code in riana-oblok9-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

riana-oblok9-breki is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with derivative packages. The primary function of these packages is to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in riana-oblok9-breki stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these compromised packages. The malicious payload is designed to continuously republish variants, exacerbating the issue and making it difficult to track and manage.

How To Fix

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

npm uninstall riana-oblok9-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 riana-oblok9-breki package and monitor your project for any dependencies that may inadvertently include it. You can also utilize tools like Vulert to monitor your package-lock.json file for vulnerabilities. To check if your application is affected by this vulnerability, visit the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The riana-oblok9-breki package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your projects from potential risks associated with compromised packages.

See every vulnerability recorded for riana-oblok9-breki →

Share this vulnerability

FAQ

riana-oblok9-breki is an npm package involved in a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and instability to your project.

You should uninstall the riana-oblok9-breki package immediately and check your project dependencies for any related vulnerabilities.

Yes, regularly update your packages, monitor your dependencies, and use tools like Vulert to stay informed about vulnerabilities.

Vulert is a tool that monitors your package-lock.json file for open-source vulnerabilities in real-time, helping you maintain the security of your software without requiring code access.

How To Fix

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

npm uninstall riana-oblok9-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