Critical Malicious Code Vulnerability in zapier-scripts Package

zapier-scripts Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190861: Malicious code in zapier-scripts (npm). Affects zapier-scripts versions 7.8.3 – 7.8.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 zapier-scripts package is a tool used within the npm ecosystem for automating workflows and integrating various applications through Zapier. It is designed to facilitate seamless connections between different services, enabling users to create automated tasks without extensive coding knowledge. However, this package has been identified as containing malicious code, posing significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the zapier-scripts package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it may lead to complete control of the affected system by an external entity. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall zapier-scripts

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

Currently, there are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package entirely.

Conclusion

The zapier-scripts package has been identified as containing malicious code, posing a significant security risk to users. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring of dependencies is essential to prevent future vulnerabilities.

See every vulnerability recorded for zapier-scripts →

Share this vulnerability

FAQ

You should uninstall the zapier-scripts package immediately and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Failure to remove the package may result in unauthorized access to your system and sensitive data, leading to potential data breaches.

Regularly monitor your dependencies using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

While many npm packages are safe, it is crucial to vet packages and monitor them for vulnerabilities regularly to ensure security.

How To Fix

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

npm uninstall zapier-scripts

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