Critical Malicious Code Vulnerability in binadit Package

binadit Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15688: Malicious code in binadit (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 binadit package is an npm library designed for facilitating binary data manipulation in JavaScript applications. It offers various functionalities that allow developers to handle binary data efficiently. However, the package has been found to contain malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the binadit package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue affects all versions of the package starting from its introduction, making it critical for users to take immediate action.

How To Fix

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

npm uninstall binadit

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 binadit package from your project until a secure version is released. You can remove it using the following command: 'npm uninstall binadit'. This will prevent any potential exploitation of the vulnerability while you await a fix.

Conclusion

The binadit package has been identified as containing malicious code, posing a serious security risk to applications that utilize it. Immediate action is required to either update or remove the package to mitigate potential threats. Regular monitoring and utilizing tools like Vulert can help in maintaining the security of your software.

See every vulnerability recorded for binadit →

Share this vulnerability

FAQ

The vulnerability involves malicious code embedded within the binadit package, which can lead to security breaches.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If an immediate update is not possible, consider removing the package from your project as a temporary measure.

Currently, there is no specific patched version mentioned, so it is crucial to monitor the package repository for updates.

Using the compromised package can lead to unauthorized access to sensitive data, data loss, or other malicious activities that can severely impact your application.

How To Fix

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

npm uninstall binadit

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