Malicious Code Injection in ocha-sambel11-breki Package

ocha-sambel11-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74712: Malicious code in ocha-sambel11-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The ocha-sambel11-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that has been flooding the npm registry with malicious packages. Its functionality is compromised, leading to potential security risks for developers and users relying on it.

Vulnerability Detail

The vulnerability in the ocha-sambel11-breki package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants to pollute the npm registry. This can lead to reputation inflation for malicious actors and potentially expose users to further security risks.

How To Fix

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

npm uninstall ocha-sambel11-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-sambel11-breki package from your project by executing: npm uninstall ocha-sambel11-breki. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The ocha-sambel11-breki package poses a significant security risk due to its malicious code injection. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for ocha-sambel11-breki →

Share this vulnerability

FAQ

The ocha-sambel11-breki package is an npm package that has been identified as part of a malicious campaign targeting developers through token rewards.

This vulnerability can compromise your project's integrity by introducing malicious code, which may lead to security breaches and reputation damage.

If you have installed the ocha-sambel11-breki package, it is crucial to uninstall it immediately and monitor your project for any unusual behavior.

Yes, you can prevent future vulnerabilities by regularly updating your packages, using tools like Vulert to monitor for vulnerabilities, and reviewing package dependencies carefully.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by vulnerabilities without requiring access to the code or installation.

How To Fix

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

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