Critical Malicious Code Vulnerability in activemerchant Package
Summary
MAL-2025-14047: Malicious code in activemerchant (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 activemerchant package is a popular library in the npm ecosystem, primarily used for handling payment processing in web applications. It provides a unified interface for various payment gateways, making it easier for developers to integrate payment solutions. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that utilize it.
Vulnerability Detail
The vulnerability in the activemerchant package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other malicious activities, potentially affecting both developers and end-users. The issue is particularly concerning as it affects all versions starting from 0, making it critical for users to address this vulnerability immediately.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall activemerchantIf 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 temporary measure, consider removing the activemerchant package from your project until a secure version is released. You can do this by running: npm uninstall activemerchant. Additionally, explore alternative payment processing libraries that do not have known vulnerabilities.
Conclusion
The activemerchant package has been found to contain malicious code, posing serious security risks to applications that utilize it. It is crucial for developers to update the package to a secure version or consider alternative solutions to mitigate potential threats. Utilizing tools like Vulert can help monitor and alert for vulnerabilities in real-time.
See every vulnerability recorded for activemerchant →
FAQ
The activemerchant package is a library used for payment processing in web applications, providing a unified interface for various payment gateways.
The malicious code can lead to unauthorized access and data breaches, posing significant risks to applications that use this package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you cannot update the package right away, consider removing it from your project and using an alternative library until a secure version is available.
More details about the vulnerability can be found on the GitHub repository of the malicious packages project, specifically at https://github.com/ossf/malicious-packages.
