Critical Malicious Code Vulnerability in @3kali182/selenium-webdriver4 Package

Summary

12/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5984: Malicious code in @3kali182/selenium-webdriver4 (npm). Affects @3kali182/selenium-webdriver4 versions >= 99.9.9. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @3kali182/selenium-webdriver4 package is an npm library that provides a WebDriver API for automating web applications for testing purposes. It is designed to facilitate browser automation, allowing developers to write scripts that interact with web pages. However, this package has been identified as containing malicious code, posing significant risks to systems that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the @3kali182/selenium-webdriver4 package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information, including secrets and keys stored on the system. The malicious nature of the code indicates that it was intentionally designed to exploit vulnerabilities in the system, leading to severe security breaches.

How To Fix

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

npm uninstall @3kali182/selenium-webdriver4

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 avoid using the @3kali182/selenium-webdriver4 package altogether. If your project relies on its functionality, consider looking for alternative packages that provide similar capabilities without the associated risks.

Conclusion

The @3kali182/selenium-webdriver4 package contains malicious code that poses significant risks to any system using it. Immediate action is required to uninstall the package and secure any sensitive information. Monitoring tools like Vulert can assist in identifying vulnerabilities in your applications.

See every vulnerability recorded for @3kali182/selenium-webdriver4 →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any secrets or keys stored on your system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

As of now, there is no patched version available. The recommended action is to uninstall the package.

Failing to address this vulnerability can lead to unauthorized access to sensitive information and complete compromise of your system.

It is advisable to find alternative packages that offer similar functionality without the associated risks of malicious code.

How To Fix

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

npm uninstall @3kali182/selenium-webdriver4

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