Which versions of @trigo/trigo-hapijs are malicious?

The following npm versions of @trigo/trigo-hapijs are flagged malicious: 5.0.1. Treat any of these as compromised.

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

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

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

Yes — @trigo/trigo-hapijs is associated with the GHSA-pcgx-2p87-9rfg 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/trigo-hapijs 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/trigo-hapijs (version 5.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @trigo/trigo-hapijs across your stack and pipelines.

Malicious package

@trigo/trigo-hapijsnpm

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

MAL-2025-190690

Immediate action

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

npm uninstall @trigo/trigo-hapijs

What this malware does

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

5.0.1

Indicators of compromise (SHA-256)

384fe54f516562597d9788351e6c7a029c9103f650f18e1cd8d977634c142199

5c7e81e80711c8a06b45fdcf920330f28c7da02f8080f179ee1161717bdc2a78

19e073277e72ea37690b3ca4607f4af3716c280a4fe3ab4d505ee3abf3d35bfc

d5aecc6c93d7ac1c0ae138218926b1f083c1a32ed8d0cfb7c7da6e5783f395d3

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

Campaign

GHSA-pcgx-2p87-9rfg

References

Credits

Amazon Inspector · finder

Detect & block this

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