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

Summary

22/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2043: Malicious code in @emilgroup/commission-sdk-node (npm). Affects @emilgroup/commission-sdk-node versions 1.0.3. 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/commission-sdk-node package is an npm library designed to facilitate commission calculations and management within Node.js applications. It provides developers with tools to integrate commission functionalities seamlessly. However, this package has been compromised, embedding malicious code that poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the @emilgroup/commission-sdk-node package, specifically version 1.0.3. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information, including secrets and keys. The implications of this vulnerability are severe, as it can lead to data breaches and unauthorized control over affected systems.

How To Fix

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

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

There are no effective workarounds for this vulnerability. The only recommended action is to uninstall the package and secure your system.

Conclusion

The @emilgroup/commission-sdk-node package has been identified as containing malicious code that compromises the security of any system using it. Immediate uninstallation and security measures are necessary to mitigate the risks associated with this vulnerability.

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

Share this vulnerability

FAQ

You should immediately uninstall the package using 'npm uninstall @emilgroup/commission-sdk-node' and rotate any sensitive information stored on your system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

The risks include unauthorized access to sensitive information, potential data breaches, and complete control over the compromised system.

Currently, there is no patched version available for this package. It is recommended to uninstall it immediately.

You should rotate all secrets and keys stored on the affected computer from a different, secure system to prevent unauthorized access.

How To Fix

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

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