Malicious Code Detected in bloomr Package - Security Alert

bloomr Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15852: Malicious code in bloomr (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 bloomr package is an npm library designed for creating and managing bloom filters, which are space-efficient probabilistic data structures used for membership testing. It is commonly utilized in applications requiring quick lookups with minimal memory usage. However, recent findings have revealed that the package contains malicious code, posing a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability in the bloomr package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access to sensitive data, lead to data corruption, or enable other malicious activities. The issue affects all versions of the package starting from its introduction, making it imperative for users to take 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 bloomr

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 bloomr package from your project until a secure version is released. You can do this by running the following command: npm uninstall bloomr. This will help mitigate the risk associated with the malicious code while you await a fix.

Conclusion

The bloomr package has been identified to contain malicious code, which poses a serious threat to applications using it. Users are strongly advised to update or remove the package to safeguard their applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for bloomr →

Share this vulnerability

FAQ

The bloomr package is used for creating and managing bloom filters, which are efficient data structures for membership testing in applications.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, it can identify if your application is affected.

If an immediate update is not possible, consider removing the bloomr package from your project as a temporary measure to avoid potential security risks.

Detailed information about the vulnerability can be found in the Open Source Vulnerability database, specifically at the provided GitHub link.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall bloomr

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