Malicious Code Vulnerability in escaux Package

escaux Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1728: Malicious code in escaux (npm). Affects escaux versions 999.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 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 escaux package is a Node.js library designed for integrating with the Escaux communication platform, providing functionalities for managing communication services. It is widely used in applications that require telephony and messaging capabilities. However, the package has been identified to contain malicious code that poses a significant security risk to users.

Vulnerability Detail

The vulnerability in the escaux package is characterized by the presence of malicious code that can compromise the integrity of applications utilizing this library. This issue originated from a malicious actor who introduced harmful code into version 999.0.0 of the package. The ramifications of this vulnerability can include unauthorized access to sensitive data, data corruption, and potential system compromise. It is crucial for developers to be aware of this vulnerability to prevent exploitation.

How To Fix

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

npm uninstall escaux

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, users can remove the escaux package from their project until a secure version is confirmed. This can be done using the command: npm uninstall escaux. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The escaux package has been identified with a serious vulnerability due to malicious code. It is imperative for users to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for escaux →

Share this vulnerability

FAQ

The escaux package is used for integrating with the Escaux communication platform, enabling telephony and messaging functionalities in applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.

If you are using version 999.0.0, you should uninstall the package immediately and update to the latest secure version.

The risks include unauthorized access to sensitive data, data corruption, and potential system compromise, which can lead to severe security breaches.

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions to mitigate risks.

How To Fix

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

npm uninstall escaux

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