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

@emilgroup/account-sdk Updated 22 Mar 2026

Summary

22/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2031: Malicious code in @emilgroup/account-sdk (npm). Affects @emilgroup/account-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 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/account-sdk package is a JavaScript library used in Node.js applications for managing user accounts and authentication processes. It provides functionalities such as user registration, login, and account management. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and organizations relying on it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within versions 1.41.1 to 1.41.2 of the @emilgroup/account-sdk package. This code can lead to complete system compromise, allowing unauthorized access to sensitive information such as secrets and keys stored on the affected computer. The malicious nature of the code is classified under CWE-506, indicating that it appears to be intentionally harmful. Users are advised to treat any system with this package installed as fully compromised.

How To Fix

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

npm uninstall @emilgroup/account-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 and ensuring that all sensitive information is secured. Users should also consider using alternative packages that do not have known vulnerabilities.

Conclusion

The @emilgroup/account-sdk package has been identified as containing malicious code that poses a severe risk to any system it is installed on. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their applications.

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

Share this vulnerability

FAQ

Immediately remove the package and rotate any secrets or keys stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner without needing to sign up.

As of now, versions 1.41.1 and 1.41.2 are compromised. Always check for the latest version and ensure it is secure before installation.

Failing to address this vulnerability could lead to unauthorized access to sensitive data, system compromise, and potential data breaches.

No, it is recommended to completely remove the package and replace it with a secure alternative to avoid any risks.

How To Fix

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

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