Malicious Code Detected in bmnick Package - Security Alert

bmnick Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15905: Malicious code in bmnick (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 bmnick package is an npm library that serves various functionalities within JavaScript applications. It is designed to facilitate specific tasks for developers, but it has recently been identified as containing malicious code that poses a significant security risk to users. This vulnerability can lead to unauthorized access or manipulation of sensitive data.

Vulnerability Detail

The bmnick package has been found to contain malicious code that can compromise the integrity of applications using it. This vulnerability originated from the package itself, which was introduced in version 0 and has not been addressed in subsequent releases. The ramifications of this vulnerability include potential data breaches, unauthorized access to user information, and exploitation of the affected systems. It is critical for users to be aware of this issue and take immediate action to mitigate risks.

How To Fix

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

npm uninstall bmnick

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

Currently, there are no specific workarounds to mitigate the risks associated with the bmnick package. The best course of action is to remove the package from your project and seek alternative libraries that provide similar functionality without the associated risks.

Conclusion

The bmnick package has been identified as containing malicious code that poses significant security risks. Users are strongly advised to remove the package and seek alternatives to protect their applications. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for bmnick →

Share this vulnerability

FAQ

The bmnick package is an npm library used in JavaScript applications for various functionalities, but it has been compromised with malicious code.

You can check if your application is affected by using the Vulert platform, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your package-lock.json file.

If you have the bmnick package installed, it is crucial to remove it immediately and replace it with a secure alternative.

As of now, there is no patched version of the bmnick package available. Users are advised to avoid using it.

Using the bmnick package can lead to data breaches, unauthorized access to sensitive information, and exploitation of your application.

How To Fix

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

npm uninstall bmnick

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