Malicious Code Detected in @zapier/stubtree Package - Security Risk Alert

@zapier/stubtree Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190920: Malicious code in @zapier/stubtree (npm). Affects @zapier/stubtree versions 0.1.3. 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 @zapier/stubtree package is a utility library used in Node.js applications for creating stub trees in testing environments. It is designed to facilitate the development and testing of applications by providing a simple way to mock dependencies. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @zapier/stubtree package, specifically in version 0.1.3. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The malicious code was identified by Amazon Inspector, highlighting the importance of monitoring dependencies for security threats.

How To Fix

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

npm uninstall @zapier/stubtree

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 @zapier/stubtree package from your project to mitigate the risk until a secure version is available. You can do this by executing the following command: npm uninstall @zapier/stubtree.

Conclusion

The discovery of malicious code in the @zapier/stubtree package underscores the importance of regularly monitoring and updating dependencies in software projects. By following the recommended steps to fix the vulnerability and utilizing tools like Vulert for ongoing monitoring, developers can better protect their applications from potential threats.

See every vulnerability recorded for @zapier/stubtree →

Share this vulnerability

FAQ

The @zapier/stubtree package is used in Node.js applications to create stub trees for testing purposes, allowing developers to mock dependencies easily.

The malicious code was detected by Amazon Inspector, a security tool that scans for vulnerabilities in open-source packages.

Using the compromised version can lead to unauthorized access to your application, data breaches, and other security threats.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

If you cannot update the package immediately, it is advisable to remove it from your project as a temporary measure to reduce security risks.

How To Fix

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

npm uninstall @zapier/stubtree

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