Critical Malicious Code Vulnerability in @trigo/atrix-acl Package

@trigo/atrix-acl Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190678: Malicious code in @trigo/atrix-acl (npm). Affects @trigo/atrix-acl versions 4.0.2. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @trigo/atrix-acl package is a Node.js library designed for managing access control lists (ACLs) in applications. It provides developers with tools to define and enforce permissions for various resources within their software. However, this package has been compromised, leading to severe security risks for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the @trigo/atrix-acl package. This code can fully compromise any computer where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to a malicious actor who has injected harmful code into the package, making it a significant threat to users and their systems.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @trigo/atrix-acl

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

There are no effective workarounds for this vulnerability other than removing the package entirely. Users should avoid using @trigo/atrix-acl until a secure version is released.

Conclusion

The @trigo/atrix-acl package has been compromised with malicious code, posing a significant risk to any system using it. Immediate action is required to uninstall the package and secure any sensitive information. Users should remain vigilant and monitor for updates regarding a secure version of the package.

See every vulnerability recorded for @trigo/atrix-acl →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive information stored on the affected system.

You can use the Vulert playground at Vulert Scanner to check if your application is impacted by this vulnerability without needing to sign up.

No, there is currently no patched version of the @trigo/atrix-acl package available. The only solution is to remove it.

Failure to address this vulnerability could lead to unauthorized access to sensitive data and complete control of the affected system by malicious actors.

It is highly discouraged to use @trigo/atrix-acl until a secure version is released and the vulnerability is resolved.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @trigo/atrix-acl

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback