Malicious Code Detected in boiidash Package - Security Alert

boiidash Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15932: Malicious code in boiidash (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 boiidash package is an npm library designed for utility functions in JavaScript applications. It provides various features to enhance development efficiency. However, it has been identified to contain malicious code, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the boiidash package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability is particularly concerning as it can operate without the user's knowledge, potentially affecting a wide range of applications that rely on this package.

How To Fix

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

npm uninstall boiidash

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, consider removing the boiidash package from your project until a secure version is released. You can do this by running the following command: npm uninstall boiidash. Alternatively, you may look for similar packages that provide the same functionality without the associated risks.

Conclusion

The discovery of malicious code in the boiidash package highlights the importance of regularly monitoring and updating dependencies in software projects. Users are encouraged to take immediate action by updating or removing the affected package to safeguard their applications.

See every vulnerability recorded for boiidash →

Share this vulnerability

FAQ

boiidash is an npm library that offers utility functions for JavaScript development.

The malicious code can lead to unauthorized access and potential data breaches in applications using the package.

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

Yes, you should check for a patched version of boiidash and update it using npm update boiidash.

As a workaround, consider uninstalling the boiidash package or replacing it with a safer alternative until a fix is available.

How To Fix

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

npm uninstall boiidash

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