Malicious Code Injection in ocha-klanting57-breki Package

ocha-klanting57-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74690: Malicious code in ocha-klanting57-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 ocha-klanting57-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the ocha-klanting57-breki package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to pollute the npm registry, potentially leading to reputation inflation for developers involved in the tea protocol token rewards. The origin of this vulnerability is linked to a broader campaign that exploits npm's package management system for nefarious purposes.

How To Fix

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

npm uninstall ocha-klanting57-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-klanting57-breki package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The ocha-klanting57-breki package has been identified as containing malicious code that poses a significant risk to developers and their projects. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the security and integrity of your software.

See every vulnerability recorded for ocha-klanting57-breki →

Share this vulnerability

FAQ

The ocha-klanting57-breki package is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious scripts.

The malicious code modifies your package.json file, removes private flags, and continuously republishes variants, which can lead to reputation inflation and potential security risks.

If you have installed the ocha-klanting57-breki package, you should uninstall it immediately using 'npm uninstall ocha-klanting57-breki' and check for any other affected packages.

You can use tools like Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software. Vulert requires only the package-lock.json file for analysis.

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

How To Fix

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

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