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

Summary

22/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2054: Malicious code in @emilgroup/partner-portal-sdk-node (npm). Affects @emilgroup/partner-portal-sdk-node versions >= 1.1.1, <= 1.1.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/partner-portal-sdk-node package is a Node.js SDK designed for integration with the Emil Group's partner portal. It provides developers with tools to facilitate communication and data exchange with the portal's services. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within versions 1.1.1 to 1.1.2 of the @emilgroup/partner-portal-sdk-node package. This code can lead to complete system compromise, allowing unauthorized access to sensitive information, including secrets and keys stored on the affected machine. The malicious nature of the code has been confirmed by security researchers, and it poses a significant risk to any system utilizing this package.

How To Fix

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

npm uninstall @emilgroup/partner-portal-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 you need to maintain functionality while removing the package, consider using an alternative SDK that provides similar capabilities without the associated risks. Always ensure to audit third-party packages for vulnerabilities before installation.

Conclusion

The @emilgroup/partner-portal-sdk-node package has been found to contain malicious code that poses a serious security risk. 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/partner-portal-sdk-node →

Share this vulnerability

FAQ

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

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

No, there is currently no patched version available for the @emilgroup/partner-portal-sdk-node package. The only solution is to remove the package.

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

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.

How To Fix

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

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