Which versions of @trigo/eslint-config-trigo are malicious?

The following npm versions of @trigo/eslint-config-trigo are flagged malicious: 3.3.1. Treat any of these as compromised.

How do I remediate @trigo/eslint-config-trigo if I installed it?

@trigo/eslint-config-trigo 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/eslint-config-trigo — how do I know if it already compromised me?

If @trigo/eslint-config-trigo 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/eslint-config-trigo part of a known attack campaign?

Yes — @trigo/eslint-config-trigo is associated with the GHSA-v5mg-qxxx-3jxx 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/eslint-config-trigo 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/eslint-config-trigo (version 3.3.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @trigo/eslint-config-trigo across your stack and pipelines.

Malicious package

@trigo/eslint-config-trigonpm

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

MAL-2025-190684

Immediate action

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

npm uninstall @trigo/eslint-config-trigo

What this malware does

The package @trigo/eslint-config-trigo 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

3.3.1

Indicators of compromise (SHA-256)

d6bc2da54cb42e905659571935f6f5e3371052a564b5dabdf468ecdbffc64b28

f323ad76d021234c96924ded9095572d18be962e0c71fb9cfbeb1fa43079e961

fbcdfebaa28adf736e6653ea11d8dce92c749dbd1a6d4e48298873f62d1ae5d1

df65de0cd431b7d9915c1ddb068160aa9671d89471cbdc8ab55fdf80baebdaab

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/eslint-config-trigo (version 3.3.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @trigo/eslint-config-trigo across your stack and pipelines.
If you installed it — respond
@trigo/eslint-config-trigo 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/eslint-config-trigo 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/eslint-config-trigo 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/eslint-config-trigo on npm has been identified as a malicious package (version 3.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-v5mg-qxxx-3jxx

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @trigo/eslint-config-trigo-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