Which versions of @trigo/jsdt are malicious?

The following npm versions of @trigo/jsdt are flagged malicious: 0.2.1. Treat any of these as compromised.

How do I remediate @trigo/jsdt if I installed it?

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

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

Yes — @trigo/jsdt is associated with the GHSA-7qm5-m3m4-5j5r 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/jsdt 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/jsdt (version 0.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @trigo/jsdt across your stack and pipelines.

Malicious package

@trigo/jsdtnpm

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

MAL-2025-190686

Immediate action

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

npm uninstall @trigo/jsdt

What this malware does

The package @trigo/jsdt 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.2.1

Indicators of compromise (SHA-256)

91f1b0ba55c42b887eade435580838bef529a7fe7a9b9fd8b3cd05ada0528cc7

ff5aae2e5762514a4d2a304a2ceb36d9b895c8bd88c9a6303752aea4b078119f

77a4bf75268e6ff69ce69490f5c7065a79fbd8ebd8db196c03898aa00828a0e4

0deafe77dfb2dfaffafbd170a5ec0a75519585b5b350012368325e73eefaab33

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

Campaign

GHSA-7qm5-m3m4-5j5r

References

Credits

Amazon Inspector · finder

Detect & block this

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