Malicious Code Detected in erick-kue2-breki Package - Security Alert

erick-kue2-breki Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19770: Malicious code in erick-kue2-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 erick-kue2-breki package is an npm library that is used for various functionalities within JavaScript applications. It is designed to facilitate certain tasks, but it has been found to contain malicious code that poses a significant security risk to users and their applications. This vulnerability can lead to unauthorized access, data breaches, and other malicious activities.

Vulnerability Detail

The vulnerability in the erick-kue2-breki package originates from the inclusion of malicious code within its source. This code can execute harmful actions without the user's consent, potentially compromising sensitive data and system integrity. Users of this package are at risk of exploitation, which can lead to severe consequences such as data loss, unauthorized access, and system corruption.

How To Fix

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

npm uninstall erick-kue2-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, avoid using the erick-kue2-breki package in your projects. If you need similar functionality, consider looking for alternative packages that are well-reviewed and have a good security track record.

Conclusion

The erick-kue2-breki package has been identified as containing malicious code, posing significant security risks to users. Immediate action is required to remove the package and seek alternatives. Regular monitoring of dependencies is crucial to maintaining application security.

See every vulnerability recorded for erick-kue2-breki →

Share this vulnerability

FAQ

erick-kue2-breki is an npm package used in JavaScript applications for various functionalities, but it has been identified to contain malicious code.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground.

If you have installed the erick-kue2-breki package, you should remove it immediately and look for alternative packages that do not pose security risks.

Currently, there is no patched version available for the erick-kue2-breki package. It is advised to remove the package until a secure version is released.

To prevent similar vulnerabilities, regularly monitor your dependencies using tools like Vulert, and keep your packages updated to their latest secure versions.

How To Fix

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

npm uninstall erick-kue2-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