Critical Malicious Code Vulnerability in wb3 Package

wb3 Updated 02 Oct 2025

Summary

16/10/2024
CRITICAL
No i
Critical
Not published

MAL-2024-10192: Malicious code in wb3 (PyPI). Affects wb3 versions 1.0.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 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 wb3 package, available on PyPI, is designed for web-based applications, providing essential functionalities for developers. However, it has recently been identified as having a critical vulnerability that exposes users to potential malicious code execution. This vulnerability affects version 1.0.0 of the package, making it imperative for users to take immediate action to secure their applications.

Vulnerability Detail

The vulnerability in the wb3 package stems from the inclusion of malicious code that can compromise the integrity of applications using this package. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue was reported by ReversingLabs and is classified under the identifier MAL-2024-10192. Users of wb3 are at risk if they continue to use the compromised version without taking corrective measures.

How To Fix

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

pip 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

If immediate updating is not feasible, consider removing the wb3 package from your project until a secure version is available. You can do this by running: pip uninstall wb3. Additionally, monitor your application for any unusual activity that may indicate exploitation of the vulnerability.

Conclusion

The wb3 package has been identified as having a critical vulnerability due to malicious code. Users must take immediate action to update or remove the package to protect their applications from potential threats. Regular monitoring and using tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for wb3 →

Share this vulnerability

FAQ

The wb3 package is utilized in web-based applications to provide various functionalities for developers.

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

If you cannot update the package immediately, consider uninstalling it and monitoring your application for any suspicious activity.

The vulnerability was discovered by ReversingLabs, a cybersecurity firm specializing in threat intelligence.

Currently, the only affected version is 1.0.0. Users should update to the latest version as soon as it is released.

Related vulnerabilities

Recent vulnerabilities recorded for wb3.

How To Fix

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

pip 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