Malicious Code Detected in bollman Package - Security Alert

bollman Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

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

Vulnerability Detail

The vulnerability in the bollman package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability makes it critical for developers to address it promptly to safeguard their applications.

How To Fix

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

npm uninstall bollman

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 remove the bollman package from your project until a secure version is released. Use the following command to uninstall it: 'npm uninstall bollman'. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the bollman package highlights the importance of regularly monitoring and updating dependencies in software projects. Developers are urged to take immediate action to mitigate risks associated with this vulnerability by updating or removing the affected package.

See every vulnerability recorded for bollman →

Share this vulnerability

FAQ

The bollman package is an npm library used for specific functionalities in JavaScript applications, 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 your application without any signup.

If you cannot update the package right away, consider removing it from your project as a temporary workaround until a secure version is available.

Yes, you can use tools like Vulert, which allows you to monitor your package-lock.json for vulnerabilities in real-time.

Using the compromised bollman package can lead to unauthorized access, data breaches, and other security issues within your application.

How To Fix

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

npm uninstall bollman

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