Which versions of tdspt-helper are malicious?

The following npm versions of tdspt-helper are flagged malicious: 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6. Treat any of these as compromised.

How do I remediate tdspt-helper if I installed it?

Remove tdspt-helper from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed tdspt-helper — how do I know if it already compromised me?

If tdspt-helper 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 tdspt-helper part of a known attack campaign?

Yes — tdspt-helper is associated with the GHSA-wv8c-8vpg-rc5x 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 tdspt-helper 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 tdspt-helper (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tdspt-helper across your stack and pipelines.

Malicious package

tdspt-helpernpm

Malicious code in tdspt-helper (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191544

Immediate action

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

npm uninstall tdspt-helper

What this malware does

The package tdspt-helper 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.

Malicious versions

6 flagged

3.2.13.2.23.2.33.2.43.2.53.2.6

Indicators of compromise (SHA-256)

b3fbe7c3c4241a699aa4e7bcd9abdaf9fdb9f37eb27d178e235db8f5ee4402a2

df7e9f891a48c1bea4bde6673484ff604dfe90e6e99972469417fbec69d0eac4

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tdspt-helper (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tdspt-helper across your stack and pipelines.
If you installed it — respond
Remove tdspt-helper from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tdspt-helper 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 tdspt-helper 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. tdspt-helper on npm has been identified as a malicious package (versions 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wv8c-8vpg-rc5x

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tdspt-helper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring