Malicious Code Detected in @zapier/spectral-api-ruleset - Security Alert

@zapier/spectral-api-ruleset Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190919: Malicious code in @zapier/spectral-api-ruleset (npm). Affects @zapier/spectral-api-ruleset versions 1.9.1 – 1.9.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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package @zapier/spectral-api-ruleset is a component of the npm ecosystem, primarily used for defining and enforcing API rules. It is designed to help developers ensure that their APIs adhere to specified standards and best practices. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the package @zapier/spectral-api-ruleset, which has been identified to contain malicious code. This code can potentially compromise the integrity of applications that depend on it, leading to unauthorized access, data breaches, or other malicious activities. The affected versions include 1.9.1, 1.9.2, and 1.9.3, and it was reported by Amazon Inspector, highlighting the need for immediate attention from developers using this package.

How To Fix

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

npm uninstall @zapier/spectral-api-ruleset

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

If immediate updating is not feasible, consider removing the package from your project until a secure version is available. You can do this by executing the following command: npm uninstall @zapier/spectral-api-ruleset.

Conclusion

The discovery of malicious code in the @zapier/spectral-api-ruleset package poses a significant risk to applications utilizing it. Developers are urged to take immediate action by updating to a secure version or removing the package altogether. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for @zapier/spectral-api-ruleset →

Share this vulnerability

FAQ

The malicious code can compromise application security, potentially leading to unauthorized access or data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

The affected versions include 1.9.1, 1.9.2, and 1.9.3.

Consider uninstalling the package temporarily until a secure version is released. Use the command: npm uninstall @zapier/spectral-api-ruleset.

The vulnerability was reported by Amazon Inspector, a security assessment service.

How To Fix

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

npm uninstall @zapier/spectral-api-ruleset

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