Critical Vulnerability in selenium-session: Malicious Code Injection

selenium-session Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191421: Malicious code in selenium-session (npm). Affects selenium-session versions 1.0.5. 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 selenium-session package is an npm library designed to facilitate browser automation using Selenium WebDriver. It allows developers to manage browser sessions efficiently. However, this package has been compromised, making it susceptible to malicious attacks that can lead to severe security breaches.

Vulnerability Detail

The vulnerability stems from a malicious code injection by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal sensitive tokens and credentials from users and publish them to GitHub. Additionally, it can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. The malicious payload poses a significant risk as it may also delete the user's home directory, leading to data loss.

How To Fix

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

npm uninstall selenium-session

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 workaround, you can remove the selenium-session package from your project until a secure version is released. Use the following command to uninstall it: npm uninstall selenium-session.

Conclusion

The selenium-session package has been compromised by a malicious worm that poses significant security risks. It is essential for users to update their packages and monitor their applications for vulnerabilities to safeguard their data and credentials.

See every vulnerability recorded for selenium-session →

Share this vulnerability

FAQ

The vulnerability involves malicious code that steals user credentials and can delete files from the user's home directory.

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

Immediately update the selenium-session package to a secure version using the command: npm update selenium-session.

Yes, the worm can propagate itself to other npm packages owned by the user, increasing the risk of widespread compromise.

Consequences include unauthorized access to sensitive information, data loss, and potential damage to the user's development environment.

How To Fix

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

npm uninstall selenium-session

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