Malicious code in @zscaler/api-enums (npm)

@zscaler/api-enums Updated 02 Oct 2025

Summary

09/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8487: Malicious code in @zscaler/api-enums (npm). Affects @zscaler/api-enums versions 5.0.0. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @zscaler/api-enums package is an npm package that provides a set of enums for Zscaler API. It is used to interact with the Zscaler platform and perform various operations. The package is widely used by developers to integrate Zscaler functionality into their applications.

Vulnerability Detail

The @zscaler/api-enums package version 5.0.0 has been identified as malicious. The package communicates with a domain associated with malicious activity and executes commands that are linked to malicious behavior. This vulnerability poses a significant risk to applications that depend on this package, as it can potentially lead to unauthorized access, data breaches, or other malicious activities.

How To Fix

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

npm uninstall @zscaler/api-enums

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

There is no known workaround for this vulnerability. It is crucial to remove the malicious package and replace it with a safe version as soon as possible.

Conclusion

The @zscaler/api-enums package version 5.0.0 has been identified as malicious and poses a significant risk to applications. It is crucial to remove this package and replace it with a safe version to mitigate the vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for @zscaler/api-enums →

Share this vulnerability

FAQ

The @zscaler/api-enums package is an npm package that provides a set of enums for Zscaler API. It is used to interact with the Zscaler platform and perform various operations.

This vulnerability can lead to unauthorized access, data breaches, or other malicious activities in applications that depend on the @zscaler/api-enums package version 5.0.0.

To fix this vulnerability, remove the @zscaler/api-enums package version 5.0.0 from your application and update to a safe version that has been patched to address this issue.

No, there is no known workaround for this vulnerability. It is crucial to remove the malicious package and replace it with a safe version.

For more information about this vulnerability and its impact, you can visit the Vulert Playground at Vulert Scanner

How To Fix

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

npm uninstall @zscaler/api-enums

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