Malicious Code Vulnerability in ogi-botok87-breki Package

ogi-botok87-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74726: Malicious code in ogi-botok87-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 ogi-botok87-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. However, it has been identified as malicious due to its ability to modify package metadata and republish variants, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability in the ogi-botok87-breki package originates from its malicious intent to manipulate the npm registry. It includes scripts that remove private flags from package.json, alters version numbers, and generates random package names, which can lead to the proliferation of unwanted packages in the registry. This can compromise the integrity of the npm ecosystem and affect developers relying on legitimate packages.

How To Fix

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

npm uninstall ogi-botok87-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 package by using npm's package-lock.json to monitor dependencies. If you are using Vulert, you can check your application for vulnerabilities without needing to access the code. Use the Vulert playground at https://vulert.com/scanner to see if your application is affected.

Conclusion

The ogi-botok87-breki package poses a significant risk due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for ogi-botok87-breki →

Share this vulnerability

FAQ

The ogi-botok87-breki package is an npm package involved in the tea.xyz token reward campaign, designed to generate and publish derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially affecting the integrity of your project's dependencies and increasing the risk of using malicious packages.

You should remove the ogi-botok87-breki package from your project and monitor for any updates or patches that may address this vulnerability.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this or other vulnerabilities.

How To Fix

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

npm uninstall ogi-botok87-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