Malicious Code Injection in hendra-oblok56-breki Package

hendra-oblok56-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73395: Malicious code in hendra-oblok56-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

The hendra-oblok56-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. This behavior poses significant risks to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in the hendra-oblok56-breki package originates from its association with the tea.xyz token reward campaign. It includes malicious scripts that modify the package.json file to remove private flags, alter version numbers, and create random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to the installation of compromised packages by unsuspecting developers. The ramifications include potential security breaches, loss of data integrity, and damage to developer reputations.

How To Fix

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

npm uninstall hendra-oblok56-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 hendra-oblok56-breki package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files to identify and remove any suspicious packages.

Conclusion

The hendra-oblok56-breki package presents a significant security risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to be vigilant about the packages they use and to regularly audit their dependencies. By following the recommended steps to remove the vulnerable package and utilizing tools like Vulert, developers can better protect their applications from similar threats.

See every vulnerability recorded for hendra-oblok56-breki →

Share this vulnerability

FAQ

The hendra-oblok56-breki package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

This vulnerability can lead to the installation of compromised packages, which may introduce security risks, data integrity issues, and damage to your application's reputation.

If you have installed the hendra-oblok56-breki package, you should uninstall it immediately using the command: npm uninstall hendra-oblok56-breki.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access or installation.

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

How To Fix

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

npm uninstall hendra-oblok56-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