Critical Malicious Code Vulnerability in @emilgroup/customer-sdk Package

@emilgroup/customer-sdk Updated 22 Mar 2026

Summary

22/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2044: Malicious code in @emilgroup/customer-sdk (npm). Affects @emilgroup/customer-sdk versions >= 1.54.1, <= 1.54.2. 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 @emilgroup/customer-sdk is an npm package designed to facilitate customer interactions and integrations within applications. It provides various functionalities that enhance user experience and streamline customer management processes. However, this package has been identified to contain malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within versions 1.54.1 to 1.54.2 of the @emilgroup/customer-sdk package. This code can compromise the entire system where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to complete system takeover by an external entity, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall @emilgroup/customer-sdk

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 measure, users can remove the @emilgroup/customer-sdk package from their project to mitigate the risk of exploitation. This can be done using the following command: npm uninstall @emilgroup/customer-sdk. However, please note that removing the package may not eliminate all malicious software that may have been installed as a result of using it.

Conclusion

The @emilgroup/customer-sdk package has been identified as containing malicious code, posing a significant security risk to users. Immediate action is required to mitigate potential damage, including uninstalling the package and rotating sensitive information. Users are encouraged to stay informed and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for @emilgroup/customer-sdk →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on the affected system.

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

Yes, it is recommended to update to a version of the package that does not contain the malicious code. Use 'npm install @emilgroup/customer-sdk@latest' to update.

Failure to address this vulnerability can lead to unauthorized access to sensitive data, complete system compromise, and potential data breaches.

It is advisable to exercise caution and monitor the package for any further vulnerabilities. Always ensure you are using the latest, secure version.

How To Fix

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

npm uninstall @emilgroup/customer-sdk

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