Malicious Code in bitboxapp (npm)

bitboxapp Updated 02 Oct 2025

Summary

05/12/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8665: Malicious code in bitboxapp (npm). Affects bitboxapp versions 1.9.0. 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

bitboxapp is an npm package that is used for [provide brief description of the package's functionality and key attributes]. It is widely used in [mention relevant industries or applications]. The package version 1.9.0 has been identified as malicious by the OpenSSF Package Analysis project.

Vulnerability Detail

The package has been flagged as malicious due to the following reasons:

  • The package communicates with a domain associated with malicious activity.
  • The package executes one or more commands associated with malicious behavior.

This vulnerability poses a significant risk to systems that have the affected version of bitboxapp installed. It can potentially lead to [describe potential ramifications of the vulnerability].

How To Fix

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

npm uninstall bitboxapp

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

There is no known workaround for this vulnerability. It is crucial to address the issue by following the recommended steps for fixing the vulnerability.

Conclusion

The bitboxapp package version 1.9.0 has been identified as malicious. It is crucial to update or remove this version from your project to mitigate the risk of potential malicious activity. For further support and assistance, please contact DevNack.com.

See every vulnerability recorded for bitboxapp →

Share this vulnerability

FAQ

bitboxapp is an npm package that [provide a brief description of the package's functionality and purpose].

This vulnerability can potentially [describe potential consequences or impact on the system]. It is important to take immediate action to mitigate the risk.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply input your package-lock.json file and Vulert will provide real-time alerts for open-source vulnerabilities.

Yes, it is recommended to update the bitboxapp package to a non-malicious version. Ensure that you are using the latest version of the package to mitigate the risk.

For further support on vulnerability remediation, you can reach out to info@devnack.com. Our team will be happy to assist you.

How To Fix

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

npm uninstall bitboxapp

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