Critical Malicious Code Vulnerability in wbnr-probe-visible-check Package

wbnr-probe-visible-check Updated 28 Sep 2026

Summary

28/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17212: Malicious code in wbnr-probe-visible-check (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 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 wbnr-probe-visible-check package is an npm library designed to assist developers in determining the visibility of web elements. It is commonly used in web applications to enhance user experience by ensuring that important elements are visible to users. However, this package has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the wbnr-probe-visible-check package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code has been confirmed by security researchers, indicating that all systems utilizing this package should be considered at risk.

How To Fix

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

npm uninstall wbnr-probe-visible-check

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, there are no effective workarounds to mitigate the risks associated with this vulnerability other than removing the package entirely. It is recommended to monitor your application for any signs of compromise and to implement security measures to protect sensitive data.

Conclusion

The wbnr-probe-visible-check package has been identified as containing malicious code that poses a significant security threat. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for wbnr-probe-visible-check →

Share this vulnerability

FAQ

You should uninstall the package immediately and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

No, there is currently no patched version available for this package.

Failure to remove the package can lead to unauthorized access to sensitive data and complete compromise of the affected system.

It is highly recommended to find an alternative package that provides similar functionality without the associated security risks.

How To Fix

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

npm uninstall wbnr-probe-visible-check

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