Malicious Code Injection in hendra-sroto81-breki Package

hendra-sroto81-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-73412: Malicious code in hendra-sroto81-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 hendra-sroto81-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the presence of malicious scripts within the hendra-sroto81-breki package. These scripts are designed to modify the package.json file by removing private flags, altering version numbers, and creating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially harm developers relying on legitimate packages. The malicious nature of this package poses significant risks, including reputation damage and security breaches for users who inadvertently install it.

How To Fix

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

npm uninstall hendra-sroto81-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-sroto81-breki package altogether. If it is already installed, you can remove it from your project by executing the following command: npm uninstall hendra-sroto81-breki.

Conclusion

The hendra-sroto81-breki package contains malicious code that poses significant risks to developers and their projects. It is crucial to remove this package and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your software by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for hendra-sroto81-breki →

Share this vulnerability

FAQ

The hendra-sroto81-breki package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, potentially compromising your project's integrity.

You should uninstall the hendra-sroto81-breki package immediately using the command: npm uninstall hendra-sroto81-breki.

Yes, you can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and review your package-lock.json file for any suspicious packages.

How To Fix

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

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