Critical Malicious Code Vulnerability in @trigo/atrix Package
Summary
MAL-2025-190677: Malicious code in @trigo/atrix (npm). Affects @trigo/atrix versions 7.0.1. 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/atrix package is a Node.js library commonly used in various applications for its functionality and ease of integration. However, it has been identified as containing malicious code that poses significant security risks to any system where it is installed. This vulnerability compromises the integrity of the system, potentially allowing unauthorized access to sensitive information.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the @trigo/atrix package, specifically version 7.0.1. This code can fully compromise any computer that has the package installed, leading to the risk of unauthorized access to secrets and keys stored on the system. The malicious nature of the code means that even after removal of the package, there is no guarantee that all malicious software has been eliminated, leaving the system vulnerable to further attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @trigo/atrixIf 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, it is recommended to avoid using the @trigo/atrix package altogether. If your application relies on its functionality, consider looking for alternative packages that provide similar features without the associated risks.
Conclusion
The @trigo/atrix package has been identified as containing malicious code that poses serious security risks. Immediate action is required to uninstall the package and secure any sensitive information. Users are encouraged to explore alternative packages and utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for @trigo/atrix →
FAQ
Immediately uninstall the package using 'npm uninstall @trigo/atrix' and rotate any sensitive keys or secrets stored on the affected system.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Failing to address this vulnerability can lead to unauthorized access to sensitive information, potential data breaches, and full system compromise.
There is no patched version available for the @trigo/atrix package. The best course of action is to uninstall it completely.
No, removing the package does not guarantee that all malicious software has been eliminated. It is essential to rotate all sensitive information stored on the system.
