Which versions of @trigo/hapi-auth-signedlink are malicious?

The following npm versions of @trigo/hapi-auth-signedlink are flagged malicious: 1.3.1. Treat any of these as compromised.

How do I remediate @trigo/hapi-auth-signedlink if I installed it?

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

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

Yes — @trigo/hapi-auth-signedlink is associated with the GHSA-r7h6-h82f-pw8f 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/hapi-auth-signedlink 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/hapi-auth-signedlink (version 1.3.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @trigo/hapi-auth-signedlink across your stack and pipelines.

Malicious package

@trigo/hapi-auth-signedlinknpm

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

MAL-2025-190829

Immediate action

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

npm uninstall @trigo/hapi-auth-signedlink

What this malware does

The package @trigo/hapi-auth-signedlink 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.3.1

Indicators of compromise (SHA-256)

2c6bc7d58766fead811090a6a02e98e0f56a2ce4c01b41f012b9860a4e1df4a0

bed6824ae90bafaade2c426612b295defed6107b61296445aa2d1d728729c23b

1bb7f2b7b5d1c6d104e06a7f5572e0ee02058f618c7cedc46e48465cdc3829aa

e68645054f1d14a1882a56ab3b58d098352cdb92ee8dd0983119a2f9386b62e5

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

Campaign

GHSA-r7h6-h82f-pw8f

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @trigo/hapi-auth-signedlink-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