Malicious Code Injection in ocha-tahu71-breki: A Threat to npm Users

ocha-tahu71-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74718: Malicious code in ocha-tahu71-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

ocha-tahu71-breki is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with derivative packages. The primary functionality of this package is to serve as a tool for developers, but its compromised nature poses significant risks to users who may unknowingly integrate it into their projects.

Vulnerability Detail

The vulnerability in ocha-tahu71-breki stems from its malicious code designed to manipulate package.json files. This code removes private flags, alters version numbers, and generates random package names, contributing to the pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of numerous derivative packages to inflate developer reputation scores. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall ocha-tahu71-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 ocha-tahu71-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The ocha-tahu71-breki package poses a significant risk due to its malicious code designed to manipulate package files and pollute the npm registry. Users are advised to uninstall the package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can provide additional security measures against such threats.

See every vulnerability recorded for ocha-tahu71-breki →

Share this vulnerability

FAQ

ocha-tahu71-breki is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing sensitive information and compromising your project's integrity.

You should immediately uninstall the package using 'npm uninstall ocha-tahu71-breki' and monitor your project for any unusual activity.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time. You can use the Vulert playground to check for vulnerabilities without needing to sign up.

If a patched version of the package is released, you can update it using 'npm update ocha-tahu71-breki'. Always check the npm registry for updates and security advisories.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall ocha-tahu71-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