Malicious Code Injection in ocha-tiwul18-breki: A Threat to npm Packages

ocha-tiwul18-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74721: Malicious code in ocha-tiwul18-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

ocha-tiwul18-breki is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. This package is designed to facilitate various functionalities within the npm ecosystem, but it has been compromised, leading to significant security concerns. The vulnerability allows for the automatic generation and publication of derivative packages, which can harm the integrity of the npm registry and developers' reputations.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the ocha-tiwul18-breki package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to the npm registry, leading to pollution and potential exploitation. The ramifications include compromised developer reputations, unauthorized access to sensitive information, and a degraded npm ecosystem.

How To Fix

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

npm uninstall ocha-tiwul18-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 remove the ocha-tiwul18-breki package from your project by executing the following command: npm uninstall ocha-tiwul18-breki. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The ocha-tiwul18-breki package has been identified as containing malicious code that poses a significant threat to the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities. Staying informed and proactive is key to maintaining a secure development environment.

See every vulnerability recorded for ocha-tiwul18-breki →

Share this vulnerability

FAQ

ocha-tiwul18-breki is an npm package involved in the tea.xyz token reward campaign, which has been compromised to include malicious code.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to reputation damage and security risks.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application against vulnerabilities using the Vulert playground without any signup.

Regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation to mitigate risks.

How To Fix

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

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