Malicious Code Injection in buyerdashboard Package

buyerdashboard Updated 16 Oct 2026

Summary

15/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17893: Malicious code in buyerdashboard (npm). Affects buyerdashboard versions 45.3.4. 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 buyerdashboard package, version 45.3.4, is designed to provide users with IP information through a dashboard interface. It is part of the npm ecosystem and is intended for use in web applications. However, this package has been found to contain malicious code that executes during the installation process, posing significant security risks to users who install it.

Vulnerability Detail

The vulnerability originates from a preinstall hook in the buyerdashboard package that executes a script (node index.js) during the npm install process. This script makes an unauthorized request to a remote server (https://realwbx.com/ip.php?ip=8.8.8.8) with a hardcoded Authorization token. This behavior indicates that the package is designed to exfiltrate user data, which can lead to data breaches and unauthorized access to sensitive information. The malicious nature of this code is classified under CWE-506, which highlights the presence of embedded malicious code.

How To Fix

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

npm uninstall buyerdashboard

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, you can prevent the preinstall script from executing by using the following command when installing the package: npm install --ignore-scripts. However, this may limit the functionality of the package.

Conclusion

The buyerdashboard package has been identified as containing malicious code that poses significant security risks. Users are advised to update or remove the package to mitigate these risks. Utilizing tools like Vulert can help in monitoring for future vulnerabilities.

See every vulnerability recorded for buyerdashboard →

Share this vulnerability

FAQ

The vulnerability involves malicious code that executes during the installation of the package, which can lead to unauthorized data access.

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

If you have installed buyerdashboard@45.3.4, it is crucial to remove the package and update to a secure version if available.

The risks include potential data breaches, unauthorized access to sensitive information, and compromise of user privacy.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

How To Fix

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

npm uninstall buyerdashboard

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