Critical Malicious Code Vulnerability in ejs-client Package

ejs-client Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19278: Malicious code in ejs-client (npm). Affected versions are not published. 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 ejs-client package is a Node.js library that facilitates the use of EJS (Embedded JavaScript) templates in client-side applications. It is widely used for rendering dynamic HTML content. However, this package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The ejs-client package has been identified to contain malicious code that can compromise the security of applications using it. This vulnerability originates from the package itself, which was introduced in version 0 and has the potential to execute harmful actions, such as data theft or unauthorized access to sensitive information. Users of this package are at risk of exploitation if they do not take immediate action.

How To Fix

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

npm uninstall ejs-client

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, consider removing the ejs-client package from your project until a secure version is available. You can do this by executing: npm uninstall ejs-client. Alternatively, you may explore using a different templating engine that does not have known vulnerabilities.

Conclusion

The ejs-client package has a critical vulnerability due to the presence of malicious code. It is essential for developers using this package to take immediate action by updating to a secure version or removing the package altogether. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for ejs-client →

Share this vulnerability

FAQ

The ejs-client package is a library for using EJS templates in client-side applications, allowing developers to render dynamic HTML content.

The vulnerability was discovered by Amazon Inspector, which identified the presence of malicious code within the ejs-client package.

The risks include potential data theft, unauthorized access to sensitive information, and exploitation of the application by malicious actors.

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

Yes, it is recommended to update the ejs-client package to the latest patched version to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall ejs-client

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