Malicious Code Injection in surya-kue58-breki: A Threat to npm Ecosystem

surya-kue58-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75523: Malicious code in surya-kue58-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 package 'surya-kue58-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'surya-kue58-breki' originates from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to create numerous derivative packages that clutter the npm registry, making it difficult for developers to find legitimate packages. The malicious payload can lead to security risks, including the potential for further exploitation of affected systems.

How To Fix

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

npm uninstall surya-kue58-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 measure, you can avoid using the 'surya-kue58-breki' package and monitor your project for any dependencies that may have been affected by this malicious code. Regularly audit your package.json and package-lock.json files for any suspicious entries.

Conclusion

The 'surya-kue58-breki' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.

See every vulnerability recorded for surya-kue58-breki →

Share this vulnerability

FAQ

It is an npm package identified as part of a malicious campaign that generates derivative packages to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may expose your project to further security risks.

You should uninstall the package immediately using 'npm uninstall surya-kue58-breki' and check your project for any other affected dependencies.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

No, there are no safe updates for 'surya-kue58-breki' as it is a malicious package. It is recommended to remove it entirely.

How To Fix

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

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