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

@emilgroup/insurance-sdk Updated 22 Mar 2026

Summary

22/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2050: Malicious code in @emilgroup/insurance-sdk (npm). Affects @emilgroup/insurance-sdk versions >= 1.97.1, <= 1.97.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 Your last release was probably never penetration tested 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/insurance-sdk is an npm package designed to facilitate insurance-related functionalities within applications. It provides developers with tools to manage insurance data and processes efficiently. However, a recent vulnerability has been discovered that compromises the security of any system utilizing this package, making it imperative for users to be aware of the risks associated with its use.

Vulnerability Detail

The vulnerability identified in the @emilgroup/insurance-sdk package is classified as malicious code embedded within the software. Originating from a malicious source, this code can fully compromise any computer that has the package installed or running. The ramifications include unauthorized access to sensitive information, such as secrets and keys stored on the affected system. Users are advised to treat any system with this package as compromised, as the malicious code may persist even after the package is removed.

How To Fix

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

npm uninstall @emilgroup/insurance-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 workaround, users should consider isolating the affected system from any sensitive data and networks until the package is removed and the system is deemed secure. Regularly monitor the system for any signs of unauthorized access.

Conclusion

The discovery of malicious code in the @emilgroup/insurance-sdk package poses a significant risk to users. Immediate action is required to remove the package and secure any compromised systems. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

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

Share this vulnerability

FAQ

Immediately remove the package and rotate any sensitive information stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Regularly update your packages and utilize tools like Vulert to monitor for vulnerabilities in real-time.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and potential system compromise.

It is recommended to find an alternative package or wait for a secure version before using it again.

How To Fix

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

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