Critical Malicious Code Vulnerability in wb3 (npm)

wb3 Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5972: Malicious code in wb3 (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 wb3 package is a Node.js library designed for various web-based functionalities, including data manipulation and API interactions. It is widely used in JavaScript applications for its ease of integration and robust feature set. However, recent findings have revealed that this package contains embedded malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the wb3 package. This code can compromise the integrity of any computer that has the package installed, potentially allowing unauthorized access to sensitive data, including secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it appears to be intentionally harmful. Users are advised to treat any system running this package as fully compromised, necessitating immediate action to secure their environments.

How To Fix

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

npm uninstall wb3

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

Currently, the best workaround is to uninstall the wb3 package entirely. You can do this by running the following command in your terminal: npm uninstall wb3. This action will help mitigate the risk associated with the malicious code until a secure version is released.

Conclusion

The wb3 package has been identified as containing malicious code, posing serious security risks to users. Immediate removal of the package and rotation of sensitive data are essential steps to mitigate these risks. Users are encouraged to stay informed about updates and patches for this package.

See every vulnerability recorded for wb3 →

Share this vulnerability

FAQ

The wb3 package is used in Node.js applications for various web functionalities, including data manipulation and API interactions.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signup.

If you have installed wb3, you should uninstall it immediately and rotate any sensitive information stored on the affected system.

As of now, there is no patched version available. Users should remove the package until a secure version is released.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, complete system compromise, and potential data breaches.

Related vulnerabilities

Recent vulnerabilities recorded for wb3.

How To Fix

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

npm uninstall wb3

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