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

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

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

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

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

Yes — @trigo/atrix-orientdb is associated with the GHSA-fh54-cv88-rhfg 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-orientdb 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-orientdb (version 1.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-orientdb across your stack and pipelines.

Malicious package

@trigo/atrix-orientdbnpm

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

MAL-2025-190680

Immediate action

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

npm uninstall @trigo/atrix-orientdb

What this malware does

The package @trigo/atrix-orientdb 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

1.0.2

Indicators of compromise (SHA-256)

9459d3d7e0bb4a45d3b778a76cb1a130d75abc57a831c7eafc7cd73fa8fdadef

dff5fee3398c42159c86cf250a0b25cae13f5e94b812aa6ef984b8fa8b4bd543

e90e36e02ebad55c62b82a6ae5b48e879b250a8daa4cdd584a5c08f69e25b674

273852b4954bcf74e2f04d7f51ea2992f4e9ea606cfe30cd7cbe415ece911f55

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-orientdb (version 1.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-orientdb across your stack and pipelines.
If you installed it — respond
@trigo/atrix-orientdb 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-orientdb 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-orientdb 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-orientdb on npm has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fh54-cv88-rhfg

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @trigo/atrix-orientdb-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