Malicious Code Injection in ogi-kue63-breki Package: A Threat to npm Users

ogi-kue63-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74738: Malicious code in ogi-kue63-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The ogi-kue63-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, which has been associated with malicious activities. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the ogi-kue63-breki package stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. This code also generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to inflate scores fraudulently. The ramifications include the potential for developers to unknowingly install compromised packages, leading to security risks in their applications.

How To Fix

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

npm uninstall ogi-kue63-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 ogi-kue63-breki package and any other packages that may be linked to the tea.xyz token reward campaign. Regularly audit your package-lock.json file to identify and remove any suspicious packages.

Conclusion

The ogi-kue63-breki package poses a significant risk due to its malicious code that modifies essential files and repackages itself under random names. It is crucial for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to monitor their projects for vulnerabilities.

See every vulnerability recorded for ogi-kue63-breki →

Share this vulnerability

FAQ

The ogi-kue63-breki package is an npm package associated with a token reward campaign that has been found to contain malicious code.

The malicious code modifies your package.json file, potentially leading to the installation of compromised packages and security vulnerabilities in your application.

You should uninstall the ogi-kue63-breki package immediately using the command npm uninstall ogi-kue63-breki.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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