Critical Malicious Code Vulnerability in @trigo/node-soap Package
Summary
MAL-2025-190688: Malicious code in @trigo/node-soap (npm). Affects @trigo/node-soap versions 0.5.4. 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 @trigo/node-soap package is an npm library designed for creating SOAP web services in Node.js applications. It simplifies the process of building and consuming SOAP services, making it a popular choice among developers. However, this package has been identified to contain malicious code, posing significant security risks to any system utilizing it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @trigo/node-soap package, specifically version 0.5.4. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The presence of this malicious code means that systems running this package should be considered fully compromised, with potential ramifications including data theft and unauthorized control over the affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @trigo/node-soapIf 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 continue using SOAP services, consider using alternative packages that do not have known vulnerabilities. You can search for other SOAP libraries on npm or consult the community for recommendations.
Conclusion
The @trigo/node-soap package has been identified as containing malicious code, posing serious security risks to any system that has it installed. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to seek alternative libraries for SOAP services to ensure their applications remain secure.
See every vulnerability recorded for @trigo/node-soap →
FAQ
Immediately uninstall the package using 'npm uninstall @trigo/node-soap' and rotate any sensitive information stored on the affected machine.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
No, there is currently no patched version available for the @trigo/node-soap package. It is recommended to remove the package and find an alternative.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and full control of the compromised system by malicious actors.
Yes, you can use alternative SOAP libraries available on npm that do not have known vulnerabilities.
