Malicious Code Injection in surya-lengko2-breki: A Threat to npm Users

surya-lengko2-breki Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75528: Malicious code in surya-lengko2-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 package 'surya-lengko2-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to a token reward campaign that has been identified as malicious. It is designed to manipulate the npm registry by generating and publishing numerous derivative packages with random names, aimed at inflating developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in 'surya-lengko2-breki' originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. This allows the package to continuously republish variants, polluting the npm registry with potentially harmful packages. The malicious payload can lead to unauthorized access, data leakage, and compromise the integrity of applications that depend on this package.

How To Fix

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

npm uninstall surya-lengko2-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 'surya-lengko2-breki' package from your project by executing the command: 'npm uninstall surya-lengko2-breki'. This will prevent any potential exploitation until a secure version is available.

Conclusion

The 'surya-lengko2-breki' package poses a significant security risk due to its malicious code that alters package files and repackages software. It is crucial for developers to take immediate action by updating or uninstalling the package to safeguard their applications. Utilizing tools like Vulert can enhance security by providing real-time vulnerability alerts.

See every vulnerability recorded for surya-lengko2-breki →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and repackages the software, leading to potential security risks.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.

Yes, the malicious payload can lead to unauthorized access and data leakage, compromising the integrity of applications.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights.

How To Fix

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

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