Malicious Code Detected in @snazah/davey: A Critical npm Vulnerability
Summary
MAL-2026-553: Malicious code in @snazah/davey (npm). Affects @snazah/davey versions 1.0.2. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package @snazah/davey is an npm package that may be used for various functionalities within JavaScript applications. However, it has been flagged for malicious behavior, specifically in version 1.0.2. This vulnerability poses a significant risk to users who have integrated this package into their projects, as it can lead to unauthorized actions and data breaches.
Vulnerability Detail
The vulnerability in @snazah/davey arises from its ability to communicate with a domain associated with malicious activity and execute commands that are harmful. This behavior can lead to severe consequences, including data theft, unauthorized access to systems, and potential compromise of user data. The vulnerability was identified by the OpenSSF Package Analysis project, which flagged the package as malicious due to its actions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @snazah/daveyIf 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 avoid using the @snazah/davey package altogether until a secure version is confirmed. If you must use it, consider isolating its usage in a controlled environment to mitigate risks.
Conclusion
The @snazah/davey package has been identified as malicious, posing significant risks to users. It is crucial to take immediate action by uninstalling the affected version and ensuring that your application is secure. Utilize tools like Vulert to monitor for vulnerabilities in your software.
See every vulnerability recorded for @snazah/davey →
FAQ
The vulnerability involves malicious code that communicates with harmful domains and executes potentially dangerous commands.
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.
You should uninstall the package immediately and update to a secure version using the provided npm commands.
No patch is available for the malicious version. The best course of action is to uninstall the affected version and install the latest version of the package.
Failure to address this vulnerability can lead to data breaches, unauthorized access to sensitive information, and compromise of your application's integrity.
