Which versions of tcsp-draw-test are malicious?

The following npm versions of tcsp-draw-test are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate tcsp-draw-test if I installed it?

tcsp-draw-test 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 tcsp-draw-test — how do I know if it already compromised me?

If tcsp-draw-test 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 tcsp-draw-test part of a known attack campaign?

Yes — tcsp-draw-test is associated with the GHSA-9pw5-2383-f23w 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 tcsp-draw-test 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 tcsp-draw-test (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tcsp-draw-test across your stack and pipelines.

Malicious package

tcsp-draw-testnpm

Malicious code in tcsp-draw-test (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191019

Immediate action

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

npm uninstall tcsp-draw-test

What this malware does

The package tcsp-draw-test 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.0.5

Indicators of compromise (SHA-256)

a0c29ab38c3bc97e4948587b9e49496e015ba0ed1f2b292e49fad4a91b6380c2

b3aab2e2be47f975ef5d6dcbb26dd22621b6043ca130bcd094aa6524696873a3

dc263e2168c90db34407f1dda4dab881468cf205b064407ac290d43005f981a1

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

Campaign

GHSA-9pw5-2383-f23w

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tcsp-draw-test-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