Malicious Code Detected in ogi-tahu54-breki: A Threat to npm Users

ogi-tahu54-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74763: Malicious code in ogi-tahu54-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 package 'ogi-tahu54-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol.

Vulnerability Detail

The vulnerability in 'ogi-tahu54-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 results in the continuous republishing of variants, which pollutes the npm registry and can lead to security risks for developers who unknowingly use these compromised packages. The malicious payload can also affect the integrity of the npm ecosystem by creating confusion and potentially introducing harmful code into projects.

How To Fix

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

npm uninstall ogi-tahu54-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 monitor your package-lock.json file for any unauthorized changes and ensure that you are only using verified packages. You can also utilize tools like Vulert to check for vulnerabilities in your project without needing to install any software. For example, you can visit the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.

Conclusion

The 'ogi-tahu54-breki' package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be vigilant, remove compromised packages, and utilize tools like Vulert to monitor their projects for vulnerabilities.

See every vulnerability recorded for ogi-tahu54-breki →

Share this vulnerability

FAQ

'ogi-tahu54-breki' is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should uninstall the package immediately using 'npm uninstall ogi-tahu54-breki' and review your project's dependencies.

Regularly update your dependencies, use trusted packages, and monitor your project with tools like Vulert to stay informed about vulnerabilities.

Vulert is a tool that monitors and alerts you in real-time for open-source vulnerabilities in your software, using just your package-lock.json file.

How To Fix

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

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