Which versions of @voiceflow/serverless-plugin-typescript are malicious?

The following npm versions of @voiceflow/serverless-plugin-typescript are flagged malicious: 2.1.7, 2.1.8. Treat any of these as compromised.

How do I remediate @voiceflow/serverless-plugin-typescript if I installed it?

@voiceflow/serverless-plugin-typescript 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 @voiceflow/serverless-plugin-typescript — how do I know if it already compromised me?

If @voiceflow/serverless-plugin-typescript was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find @voiceflow/serverless-plugin-typescript across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @voiceflow/serverless-plugin-typescript (2 malicious versions).

Part of a larger attack: @voiceflow published 57 malicious packages. See the full campaign →

Malicious package

@voiceflow/serverless-plugin-typescriptnpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

@voiceflow/serverless-plugin-typescript is a confirmed malicious npm package (MAL-2025-191373) that steals credentials and exfiltrates sensitive data (malicious versions 2.1.7, 2.1.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @voiceflow/serverless-plugin-typescript (npm)

MAL-2025-191373

Immediate action

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

npm uninstall @voiceflow/serverless-plugin-typescript

What this malware does

The package @voiceflow/serverless-plugin-typescript was found to contain malicious code.

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

2 flagged

2.1.72.1.8

Indicators of compromise (SHA-256)

20ed2f3635d9badcfe3ff16841403fc78f34608f88557c33732f284606a7fcb1

7250284d7c2e88d5fb38f55fabf16f35b8da97c4e888154f7f275f2bef975251

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @voiceflow/serverless-plugin-typescript (2 malicious versions).
If you installed it — respond
@voiceflow/serverless-plugin-typescript 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 @voiceflow/serverless-plugin-typescript was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @voiceflow/serverless-plugin-typescript on npm has been identified as a malicious package (versions 2.1.7, 2.1.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @voiceflow/serverless-plugin-typescript-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

Explore

All malware advisories How O3 detects malware Vulnerability database