Critical Malicious Code Vulnerability in universal-provider Package

universal-provider Updated 21 Jan 2026

Summary

21/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-432: Malicious code in universal-provider (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 universal-provider package is an npm library designed to facilitate the integration of various authentication providers into applications. It allows developers to streamline user authentication processes by providing a unified interface for multiple authentication methods. However, this package has been compromised, leading to significant security concerns for any application utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the universal-provider package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious code was identified through a security advisory and is classified under CWE-506, indicating that it contains code that appears to be malicious in nature. The ramifications of this vulnerability are severe, as it can lead to data breaches and unauthorized control over affected systems.

How To Fix

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

npm uninstall universal-provider

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 workaround, ensure that the universal-provider package is uninstalled from your project. You can do this by executing the following command in your terminal: npm uninstall universal-provider. Additionally, monitor your systems for any unusual activity, as the removal of the package may not eliminate all traces of the malicious code.

Conclusion

The universal-provider package has been compromised with malicious code, posing a significant risk to any systems utilizing it. Immediate action is required to remove the package and secure sensitive information. Regular monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for universal-provider →

Share this vulnerability

FAQ

The universal-provider package is an npm library that simplifies the integration of various authentication providers into applications.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

Immediately uninstall the package and rotate any secrets or keys stored on the affected system.

Currently, there is no patched version available. It is essential to remove the package entirely.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall universal-provider

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