Critical Malicious Code Vulnerability in @cda-apps/source Package
Summary
MAL-2026-336: Malicious code in @cda-apps/source (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 @cda-apps/source package is a Node.js library used in various applications for managing source code and related functionalities. It is part of the npm ecosystem, which allows developers to easily share and manage dependencies. However, this package has been identified to contain malicious code, posing significant security risks to any system that has it installed.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the @cda-apps/source package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that any computer running this package should be considered fully compromised, with potential ramifications including data theft and unauthorized control over the affected system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @cda-apps/source
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 immediate removal is not feasible, consider isolating the affected system from the network to prevent further compromise while you assess the situation. However, this is not a permanent solution and should be followed by the complete removal of the package.
Conclusion
The @cda-apps/source package has been identified as containing malicious code, posing serious security risks. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for @cda-apps/source →
FAQ
You should remove the package immediately and rotate any sensitive information stored on the affected 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.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your systems.
Yes, you can isolate the affected system from the network to prevent further compromise until you can remove the package.
While removing the package is crucial, there is no guarantee that all malicious software will be removed. It is essential to rotate all secrets and keys as well.