Malicious Code Detected in libhbaapi Package - Security Alert

libhbaapi Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-25233: Malicious code in libhbaapi (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 libhbaapi package is a Node.js library designed for interfacing with HBA (Host Bus Adapter) APIs. It is commonly used in applications that require direct communication with storage devices. However, this package has been found to contain malicious code, posing a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability in the libhbaapi package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was introduced in all versions of the package, 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 libhbaapi

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, users may consider removing the libhbaapi package from their project until a secure version is released. This can be done by executing the command: npm uninstall libhbaapi.

Conclusion

The discovery of malicious code in the libhbaapi package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action to secure their applications by updating or removing the affected package.

See every vulnerability recorded for libhbaapi →

Share this vulnerability

FAQ

libhbaapi is a Node.js library used for interfacing with Host Bus Adapter APIs, primarily for storage device communication.

The malicious code was identified by security researchers from Amazon Inspector, who reported the findings to the community.

Using the compromised package can lead to unauthorized access, data breaches, and potential exploitation of the affected systems.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.

If you are using libhbaapi, immediately uninstall the package or update it to a patched version once available to mitigate the risks.

Related vulnerabilities

Recent vulnerabilities recorded for libhbaapi.

How To Fix

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

npm uninstall libhbaapi

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