Critical Malicious Code Vulnerability in react-stickynod Package

react-stickynod Updated 02 Oct 2025

Summary

17/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6952: Malicious code in react-stickynod (npm). Affects react-stickynod versions >= 13.0.0. 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 react-stickynod package is a popular npm library used for creating sticky elements in React applications. It allows developers to easily implement sticky positioning for components, enhancing user experience by keeping important content visible during scrolling. However, this package has been identified to communicate with a domain associated with malicious activity, raising significant security concerns for users and developers alike.

Vulnerability Detail

The vulnerability stems from the react-stickynod package version 13.0.0 and later, which includes malicious code that communicates with a domain linked to harmful activities. This can lead to unauthorized data access, potential data breaches, and exploitation of user systems. The malicious behavior poses a risk not only to the applications using this package but also to the end-users interacting with those applications.

How To Fix

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

npm uninstall react-stickynod

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 react-stickynod package from your project until a secure version is released. You can do this by executing: npm uninstall react-stickynod. Consider using alternative libraries that provide similar functionality without the associated risks.

Conclusion

The react-stickynod package has a critical vulnerability that allows it to communicate with a malicious domain, posing significant risks to applications and their users. It is essential to update the package to a secure version or remove it until a fix is available. Monitoring tools like Vulert can help keep your applications safe from such vulnerabilities.

See every vulnerability recorded for react-stickynod →

Share this vulnerability

FAQ

The react-stickynod package is used to create sticky components in React applications, allowing important content to remain visible during scrolling.

The vulnerability can lead to unauthorized access to sensitive data and potential exploitation of your application, putting both your data and users at risk.

Yes, it is crucial to update the react-stickynod package to a patched version to mitigate the risks associated with this vulnerability.

If immediate updates are not possible, consider removing the package or using alternative libraries until a secure version is available.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application for vulnerabilities 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 react-stickynod

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