Malicious Code Detected in whatnot-events Package - Version 99.0.4

whatnot-events Updated 19 Mar 2026

Summary

19/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1581: Malicious code in whatnot-events (npm). Affects whatnot-events versions 99.0.4. 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 'whatnot-events' package is a JavaScript library available on npm, designed to facilitate event handling and communication in web applications. It is commonly used for managing events in real-time applications. However, version 99.0.4 has been identified as malicious, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the 'whatnot-events' package arises from its communication with a domain linked to malicious activities. This behavior can lead to unauthorized data access, potential data breaches, and compromise of user privacy. The OpenSSF Package Analysis project flagged this version as malicious due to its harmful interactions.

How To Fix

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

npm uninstall whatnot-events

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 measure, you can remove the 'whatnot-events' package from your project until a secure version is released. Use the following command to uninstall it: 'npm uninstall whatnot-events'. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'whatnot-events' package version 99.0.4 has been identified as malicious due to its communication with a harmful domain. It is essential to update or remove this package to safeguard your application from potential security threats. Utilizing tools like Vulert can help monitor your dependencies for vulnerabilities effectively.

See every vulnerability recorded for whatnot-events →

Share this vulnerability

FAQ

The package communicates with a domain known for malicious activities, which can lead to data breaches and unauthorized access.

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 immediate updates are not possible, consider uninstalling the package and using alternative solutions until a secure version is available.

While specific exploits have not been publicly disclosed, the nature of the vulnerability suggests potential for data theft and unauthorized access.

Regularly check security advisories and utilize tools like Vulert to receive real-time alerts about vulnerabilities in your dependencies.

How To Fix

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

npm uninstall whatnot-events

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