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

@emilgroup/claim-sdk-node Updated 22 Mar 2026

Summary

22/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2042: Malicious code in @emilgroup/claim-sdk-node (npm). Affects @emilgroup/claim-sdk-node versions >= 1.39.1, <= 1.39.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 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 @emilgroup/claim-sdk-node package is a Node.js SDK designed for handling claims in various applications. It provides developers with tools to integrate claim management functionalities seamlessly. However, this package has been identified as containing malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within versions 1.39.1 to 1.39.2 of the @emilgroup/claim-sdk-node package. This malicious code can compromise the entire system where the package is installed, allowing unauthorized access to sensitive information, including secrets and keys. The source of this vulnerability has been traced back to a malicious actor who has exploited the package repository, leading to potential data breaches and system integrity issues.

How To Fix

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

npm uninstall @emilgroup/claim-sdk-node

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 workaround, if immediate removal is not feasible, consider isolating the affected system from the network to prevent further exploitation. Additionally, monitor the system for any unusual activity while preparing for a complete removal of the package.

Conclusion

The @emilgroup/claim-sdk-node package has been identified as containing malicious code that compromises system security. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring and vulnerability assessments are essential to maintain system integrity.

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

Share this vulnerability

FAQ

Immediately uninstall the @emilgroup/claim-sdk-node package and rotate any sensitive credentials stored on the affected system.

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

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

There is no direct patch available for the affected versions. The recommended action is to remove the package entirely.

No, it is highly advised to remove the package regardless of current functionality, as it poses a significant security risk.

How To Fix

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

npm uninstall @emilgroup/claim-sdk-node

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