Malicious Code Injection in ocha-martabak30-breki: A Threat to npm Ecosystem

ocha-martabak30-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74698: Malicious code in ocha-martabak30-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

ocha-martabak30-breki is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores by flooding the registry with derivative packages. The package's functionality is compromised due to the presence of malicious scripts that manipulate its metadata and behavior.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the ocha-martabak30-breki package, which is designed to automatically modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes variants of the package, polluting the npm registry and potentially leading to reputational damage for developers and security risks for users who unknowingly install these compromised packages.

How To Fix

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

npm uninstall ocha-martabak30-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-martabak30-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.

Conclusion

The ocha-martabak30-breki package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying vigilant and informed can help mitigate the risks associated with such malicious packages.

See every vulnerability recorded for ocha-martabak30-breki →

Share this vulnerability

FAQ

ocha-martabak30-breki is an npm package linked to a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry with compromised packages.

You should uninstall the package immediately using 'npm uninstall ocha-martabak30-breki' and monitor your project for any further vulnerabilities.

Yes, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about security advisories related to the packages you use.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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