Malicious Code Injection in surya-menjes63-breki Package

surya-menjes63-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75534: Malicious code in surya-menjes63-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The surya-menjes63-breki package is part of the npm ecosystem, often used for various JavaScript applications. It has been identified as part of a malicious campaign associated with the tea.xyz token reward system. This package is designed to manipulate npm registry behaviors, potentially affecting developers' reputations and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the surya-menjes63-breki package stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising their projects.

How To Fix

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

npm uninstall surya-menjes63-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 prevent the installation of the surya-menjes63-breki package by using npm's package-lock.json file to lock down your dependencies. This will ensure that your project does not inadvertently install this malicious package. Additionally, you can monitor your dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time.

Conclusion

The surya-menjes63-breki package poses a significant risk due to its malicious code that manipulates npm registry behaviors. It is crucial for developers to remove this package from their projects and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for surya-menjes63-breki →

Share this vulnerability

FAQ

The surya-menjes63-breki package is an npm package that has been identified as part of a malicious campaign to manipulate npm registry behaviors.

This vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially compromising the integrity of your project.

You should uninstall the surya-menjes63-breki package immediately and check for any dependencies that may rely on it.

You can use Vulert to monitor your project for open-source vulnerabilities in real-time. It requires only the package-lock.json file for analysis.

Regularly updating your packages and using tools like Vulert can help you stay informed about vulnerabilities and protect your project.

How To Fix

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

npm uninstall surya-menjes63-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