Critical Malicious Code Vulnerability in express-sso Package

express-sso Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20084: Malicious code in express-sso (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 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 express-sso package is a Node.js library designed to facilitate single sign-on (SSO) authentication for web applications. It allows developers to integrate various authentication providers seamlessly, enhancing user experience by enabling users to log in using existing accounts from services like Google or Facebook. However, the package has been found to contain malicious code, posing significant security risks to applications utilizing it.

Vulnerability Detail

The express-sso package has been identified to contain malicious code that can compromise the security of applications using it. This vulnerability originates from the package itself, which has been tampered with to include harmful scripts. The ramifications of this vulnerability can include unauthorized access to user data, data breaches, and potential exploitation of the application for malicious purposes. It is crucial for developers to be aware of this issue and take immediate action to mitigate risks.

How To Fix

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

npm uninstall express-sso

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, consider removing the express-sso package from your project until a secure version is available. You can do this by executing the command: npm uninstall express-sso. Alternatively, you may explore other authentication libraries that do not have known vulnerabilities.

Conclusion

The express-sso package has been found to contain malicious code, posing serious security risks to applications that utilize it. Developers are urged to update the package or consider alternative solutions to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for express-sso →

Share this vulnerability

FAQ

The express-sso package is a Node.js library that enables single sign-on authentication for web applications, allowing users to log in using existing accounts from various providers.

The vulnerability in express-sso is classified as malicious code, which can lead to unauthorized access and exploitation of applications.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If you cannot update the package right away, consider removing it from your project or using an alternative authentication library until a secure version is available.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall express-sso

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