Malicious Code Detected in @spx-delivery/react Package

@spx-delivery/react Updated 16 Jan 2026

Summary

16/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-261: Malicious code in @spx-delivery/react (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @spx-delivery/react package is a JavaScript library designed for use with React applications, providing various functionalities to enhance user experience and streamline development. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the @spx-delivery/react package. This code can potentially compromise the security of applications by allowing unauthorized access or manipulation of data. The malicious nature of this code can lead to severe ramifications, including data breaches, loss of user trust, and potential legal consequences for developers and organizations using the affected package.

How To Fix

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

npm uninstall @spx-delivery/react

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 @spx-delivery/react package from your project until a secure version is available. You can do this by executing: npm uninstall @spx-delivery/react.

Conclusion

The discovery of malicious code in the @spx-delivery/react package highlights the importance of vigilance in managing open-source dependencies. By promptly addressing this vulnerability through updates and utilizing monitoring tools like Vulert, developers can safeguard their applications and maintain user trust.

See every vulnerability recorded for @spx-delivery/react →

Share this vulnerability

FAQ

The malicious code can compromise application security, potentially leading to unauthorized access and data manipulation.

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

If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to your packages.

How To Fix

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

npm uninstall @spx-delivery/react

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