Which versions of @trigo/node-soap are malicious?

The following npm versions of @trigo/node-soap are flagged malicious: 0.5.4. Treat any of these as compromised.

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

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

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

Yes — @trigo/node-soap is associated with the GHSA-4wr7-pxm7-hr89 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/node-soap 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/node-soap (version 0.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @trigo/node-soap across your stack and pipelines.

Malicious package

@trigo/node-soapnpm

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

MAL-2025-190688

Immediate action

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

npm uninstall @trigo/node-soap

What this malware does

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

0.5.4

Indicators of compromise (SHA-256)

5e716e9be0271391b5264d23544b7f5de65a55b9fdf09ef9b7c05dc2050209ac

c68fcc8b44cce3e356e21d793a260c66c48b40eb7283140b4e1e1f3ccc191660

d481bb76d1a3b03a429629953330f3db84f2aac7217424e49cb65086dcc8449e

63dfbd3e65a803cf0c8ebe0357880d32098b6aa0842c72053850764e811b655f

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

Campaign

GHSA-4wr7-pxm7-hr89

References

Credits

Amazon Inspector · finder

Detect & block this

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