Malicious Code Detected in react-toast-cold: Version 2.6.1 Vulnerability

react-toast-cold Updated 02 Feb 2026

Summary

28/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-626: Malicious code in react-toast-cold (npm). Affects react-toast-cold versions 2.6.1. 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

react-toast-cold is an npm package designed for displaying toast notifications in React applications. It provides developers with an easy way to present brief messages to users, enhancing user experience. However, version 2.6.1 of this package has been flagged for malicious behavior, raising concerns about its integrity and safety for developers and users alike.

Vulnerability Detail

The vulnerability in react-toast-cold originates from the package executing commands associated with malicious behavior. This could potentially lead to unauthorized access, data breaches, or other harmful actions within applications that utilize this package. The malicious nature of the code poses significant risks to both developers and end-users, as it compromises the security of the software relying on this package.

How To Fix

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

npm uninstall react-toast-cold

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 using an alternative package for toast notifications in React applications until a secure version of react-toast-cold is released. Some popular alternatives include 'react-toastify' or 'react-notifications-component'.

Conclusion

The discovery of malicious code in react-toast-cold version 2.6.1 highlights the importance of vigilance when using open-source packages. Developers are urged to take immediate action to secure their applications by removing the affected package and considering alternatives or updates.

See every vulnerability recorded for react-toast-cold →

Share this vulnerability

FAQ

react-toast-cold is an npm package used for displaying toast notifications in React applications.

Version 2.6.1 of react-toast-cold has been identified as malicious.

You should uninstall the affected version and update to a safe version or use an alternative package.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. It requires only the package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall react-toast-cold

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