Which versions of react-toast-cold are malicious?

The following npm versions of react-toast-cold are flagged malicious: 2.6.1. Treat any of these as compromised.

How do I remediate react-toast-cold if I installed it?

Remove react-toast-cold from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed react-toast-cold — how do I know if it already compromised me?

If react-toast-cold was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is react-toast-cold part of a known attack campaign?

Yes — react-toast-cold is associated with the GHSA-p975-whf2-4298 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find react-toast-cold across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-toast-cold (version 2.6.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-toast-cold across your stack and pipelines.

Malicious package

react-toast-coldnpm

Malicious code in react-toast-cold (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-626

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall react-toast-cold

What this malware does

The package react-toast-cold was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'react-toast-cold' @ 2.6.1 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

2.6.1

Indicators of compromise (SHA-256)

54c08af1bb9f6004862aab373a8cda6431979025c4c49104f8bd3671bb439960

10dcf80d6b6e15bcfb18c2f1a4211efd1c79f6f66e8aa34bbab7107a90d1da86

dc67550f336ea3c52946bb6d0ab4f031eee7a60cc562b0fd4220750c72f08642

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-toast-cold (version 2.6.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-toast-cold across your stack and pipelines.
If you installed it — respond
Remove react-toast-cold from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If react-toast-cold was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks react-toast-cold before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. react-toast-cold on npm has been identified as a malicious package (version 2.6.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p975-whf2-4298

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks react-toast-cold-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring