Which versions of @trigo/atrix-acl are malicious?

The following npm versions of @trigo/atrix-acl are flagged malicious: 4.0.2. Treat any of these as compromised.

How do I remediate @trigo/atrix-acl if I installed it?

@trigo/atrix-acl is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @trigo/atrix-acl — how do I know if it already compromised me?

If @trigo/atrix-acl was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @trigo/atrix-acl part of a known attack campaign?

Yes — @trigo/atrix-acl is associated with the GHSA-cmrc-89ch-44wj campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @trigo/atrix-acl across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @trigo/atrix-acl (version 4.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @trigo/atrix-acl across your stack and pipelines.

Malicious package

@trigo/atrix-aclnpm

Malicious code in @trigo/atrix-acl (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190678

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @trigo/atrix-acl

What this malware does

The package @trigo/atrix-acl was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

4.0.2

Indicators of compromise (SHA-256)

52dbc146720620532d9726aeba591e83cd1d56841d1242aeebd3f160f72c0d58

1709080673e2717f0cff39ad90b7c825ced5be2378f46a4ebdceadbf9b3f184c

d07a7e5fa0802e3e6570060db93bb884014e3493083fa4e3c8bebc2da5e37e7f

72e7a1bc7067b7cbe9238f12fd3ac99fa69f84fd3838ee0ef48977e4e36e19a5

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @trigo/atrix-acl (version 4.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @trigo/atrix-acl across your stack and pipelines.
If you installed it — respond
@trigo/atrix-acl is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @trigo/atrix-acl was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @trigo/atrix-acl before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @trigo/atrix-acl on npm has been identified as a malicious package (version 4.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cmrc-89ch-44wj

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @trigo/atrix-acl-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring