Critical Malicious Code Vulnerability in @global-dax-ad-platform/dax-components Package
Summary
MAL-2026-1165: Malicious code in @global-dax-ad-platform/dax-components (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @global-dax-ad-platform/dax-components package is a Node.js library used in various applications for ad platform functionalities. It provides components that facilitate the integration of advertising features into web applications. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on.
Vulnerability Detail
The vulnerability stems from embedded malicious code within the @global-dax-ad-platform/dax-components package. This code can lead to full system compromise, allowing attackers to gain unauthorized access to sensitive information such as secrets and keys stored on the affected machine. The malicious nature of the code means that simply removing the package may not eliminate all traces of the compromise, as attackers may have already established control over the system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @global-dax-ad-platform/dax-componentsIf 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 secrets and keys are rotated. It is essential to monitor your system for any signs of compromise after the removal.
Conclusion
The @global-dax-ad-platform/dax-components package contains a critical vulnerability due to embedded malicious code. Immediate action is required to remove the package and secure your system. Regular monitoring and auditing of dependencies are essential to prevent future vulnerabilities.
See every vulnerability recorded for @global-dax-ad-platform/dax-components →
FAQ
You should remove the package immediately and rotate any secrets or keys stored on your system.
Look for unusual activity, unauthorized access attempts, or any changes to your system that you did not initiate.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
Yes, you can use the Vulert playground at Vulert Scanner to check your application without needing to sign up.
Vulert is a tool that monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
