Critical Malicious Code Vulnerability in relay-optimizer-plugin

relay-optimizer-plugin Updated 18 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1539: Malicious code in relay-optimizer-plugin (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 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 relay-optimizer-plugin is an npm package designed to optimize relay operations in JavaScript applications. It is commonly used in various projects to enhance performance and streamline data handling. However, this package has been compromised, leading to significant security risks for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the relay-optimizer-plugin package. This code can fully compromise any computer that has the package installed or running, potentially allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to the malicious intent of the package's maintainers, making it imperative for users to 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 relay-optimizer-plugin

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 posed by this vulnerability other than removing the package and rotating sensitive credentials.

Conclusion

The relay-optimizer-plugin has been identified as containing malicious code that poses a severe security threat. Users must act swiftly to remove the package and secure their systems. Regular monitoring of dependencies is crucial to maintaining software security.

See every vulnerability recorded for relay-optimizer-plugin →

Share this vulnerability

FAQ

Immediately remove the relay-optimizer-plugin package and rotate any secrets or keys stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

As of now, there is no patched version available. The best course of action is to remove the package.

Failing to address this vulnerability could lead to unauthorized access to sensitive data, complete system compromise, and potential data breaches.

While many npm packages are safe, it is essential to monitor and audit dependencies regularly. Tools like Vulert can help you stay informed about vulnerabilities.

How To Fix

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

npm uninstall relay-optimizer-plugin

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