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

@emilgroup/claim-sdk Updated 22 Mar 2026

Summary

22/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2041: Malicious code in @emilgroup/claim-sdk (npm). Affects @emilgroup/claim-sdk versions >= 1.41.1, <= 1.41.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/claim-sdk package is an npm library designed to facilitate claims processing in applications. It provides various functionalities that help developers integrate claim management features seamlessly. However, this package has been identified as containing malicious code, posing significant security risks to any system that utilizes it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within versions 1.41.1 to 1.41.2 of the @emilgroup/claim-sdk package. Any system running this package is considered fully compromised, with potential unauthorized access to sensitive information such as secrets and keys. The malicious code may allow external entities to gain control over the affected systems, leading to severe data breaches and security incidents.

How To Fix

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

npm uninstall @emilgroup/claim-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

There are no effective workarounds for this vulnerability other than removing the package entirely. Ensure to monitor your systems for any signs of compromise after removal.

Conclusion

The @emilgroup/claim-sdk package has been compromised with malicious code, affecting versions 1.41.1 to 1.41.2. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

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

Share this vulnerability

FAQ

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. Visit Vulert Scanner to check your application without needing to sign up.

Failure to address this vulnerability may lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

It is advisable to review the security history of other packages from the same author and consider using alternatives that have a better security track record.

How To Fix

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

npm uninstall @emilgroup/claim-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