Malicious Code Vulnerability in ersagent-frontend Package

ersagent-frontend Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1726: Malicious code in ersagent-frontend (npm). Affects ersagent-frontend versions 9.5.5. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The ersagent-frontend package is a JavaScript library used in web applications to facilitate frontend development. It provides various functionalities that enhance user experience and streamline development processes. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the ersagent-frontend package stems from the inclusion of malicious code that can compromise the integrity and security of applications using this library. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of user data. The vulnerability was discovered in version 9.5.5 of the package, and it is crucial for developers to address this issue promptly to mitigate risks.

How To Fix

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

npm uninstall ersagent-frontend

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, you can remove the ersagent-frontend package from your project until a secure version is available. You can do this by executing: npm uninstall ersagent-frontend.

Conclusion

The ersagent-frontend package has been identified with a serious vulnerability due to malicious code. It is essential for developers to update the package to a secure version or remove it from their projects to protect their applications from potential threats.

See every vulnerability recorded for ersagent-frontend →

Share this vulnerability

FAQ

The ersagent-frontend package is a JavaScript library designed for frontend development in web applications, providing various tools and functionalities.

The malicious code can compromise application security, leading to unauthorized access and potential data breaches.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Yes, a patched version is available. You can update the package to the latest version using the command: npm update ersagent-frontend.

If immediate updates are not possible, consider removing the package from your project as a temporary workaround.

How To Fix

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

npm uninstall ersagent-frontend

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