Malicious Code Detected in ogi-jus79-breki: A Threat to npm Ecosystem

ogi-jus79-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74734: Malicious code in ogi-jus79-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-jus79-breki' is part of a malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered names and metadata, thereby inflating developer reputation scores for token rewards. Its functionality is primarily focused on automating the publication of these malicious variants.

Vulnerability Detail

The vulnerability in 'ogi-jus79-breki' stems from its inclusion in a series of malicious npm packages that utilize autopublish scripts to modify package.json files. These modifications include removing private flags, changing version numbers, and creating random package names, which leads to pollution of the npm registry. The origin of this vulnerability is tied to the broader tea.xyz token reward campaign that exploits the npm ecosystem for malicious purposes, potentially compromising the integrity of the registry and affecting 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-jus79-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-jus79-breki' package and monitor your package-lock.json for any unauthorized changes. If you suspect that your project has been affected, consider using tools like Vulert to scan your dependencies for vulnerabilities.

Conclusion

The 'ogi-jus79-breki' package poses a significant threat to the npm ecosystem due to its malicious intent to manipulate the registry. It is essential for developers to be vigilant, remove such packages, and utilize tools like Vulert to safeguard their projects against vulnerabilities.

See every vulnerability recorded for ogi-jus79-breki →

Share this vulnerability

FAQ

'ogi-jus79-breki' is a malicious npm package that is part of a campaign to manipulate the npm registry and inflate developer reputation scores.

The vulnerability can lead to unauthorized changes in your package.json file, potentially compromising your project's integrity and security.

You should uninstall the 'ogi-jus79-breki' package immediately and check your project for any unauthorized modifications.

Regularly update your dependencies, monitor your package-lock.json, and use tools like Vulert to scan for vulnerabilities in real-time.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check for vulnerabilities without any signup at their playground.

How To Fix

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

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