Malicious Code Detected in bolcsi Package - Immediate Action Required

bolcsi Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15935: Malicious code in bolcsi (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 bolcsi package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and lightweight nature. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the bolcsi package originates from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, or even complete system takeover. The malicious nature of the code was confirmed by security researchers, highlighting the importance of immediate action to mitigate potential risks.

How To Fix

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

npm uninstall bolcsi

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, consider removing the bolcsi package from your project until a secure version is released. You can do this by running the command: 'npm uninstall bolcsi'. This will prevent any potential exploitation of the malicious code while you seek alternative packages or await a fix.

Conclusion

The discovery of malicious code in the bolcsi package poses a serious threat to applications utilizing this npm library. It is imperative to take immediate action by updating or removing the package to safeguard your projects. Stay informed about updates and utilize tools like Vulert for ongoing monitoring.

See every vulnerability recorded for bolcsi →

Share this vulnerability

FAQ

The bolcsi package is an npm library used in JavaScript applications for specific functionalities, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Immediately update or uninstall the bolcsi package to mitigate the risks associated with the malicious code.

As of now, a patched version has not been released. Keep an eye on the package repository for updates.

Failing to address this vulnerability can lead to unauthorized access, data breaches, and significant security risks for your application.

How To Fix

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

npm uninstall bolcsi

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