Malicious Code Detected in wbcm Package - Security Alert

wbcm Updated 02 Oct 2025

Summary

28/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6780: Malicious code in wbcm (npm). Affects wbcm 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The wbcm package is a Node.js library used for various web-related functionalities. It is designed to facilitate communication and data handling in web applications. However, it has been identified to communicate with a domain associated with malicious activity, raising significant security concerns for users relying on this package.

Vulnerability Detail

The vulnerability in the wbcm package stems from its communication with a domain linked to malicious activities. This can lead to unauthorized data access, potential data breaches, and exploitation of the affected systems. The issue was introduced in version 1.0.0, making all subsequent versions vulnerable until a fix is applied. Users of this package should be aware of the risks associated with its use, especially in production environments.

How To Fix

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

npm uninstall wbcm

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 measure, users can remove the wbcm package from their project until a secure version is released. This can be done by executing the command: 'npm uninstall wbcm'. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The wbcm package has a significant vulnerability due to its communication with a malicious domain. Users should take immediate action to update or remove the package to mitigate potential security risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for wbcm →

Share this vulnerability

FAQ

The wbcm package is a Node.js library used for web-related functionalities, including data handling and communication in web applications.

The wbcm package has been found to communicate with a domain associated with malicious activity, posing security risks to users.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

It is recommended to update the wbcm package to the latest patched version or remove it from your project until a secure version is available.

You can visit the Vulert website, which provides tools to monitor and alert for vulnerabilities in open-source software.

How To Fix

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

npm uninstall wbcm

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