Which versions of @voiceflow/tsconfig-paths are malicious?

The following npm versions of @voiceflow/tsconfig-paths are flagged malicious: 1.1.4, 1.1.5. Treat any of these as compromised.

How do I remediate @voiceflow/tsconfig-paths if I installed it?

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

If @voiceflow/tsconfig-paths 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/tsconfig-paths across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @voiceflow/tsconfig-paths (2 malicious versions).

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

Malicious package

@voiceflow/tsconfig-pathsnpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

@voiceflow/tsconfig-paths is a confirmed malicious npm package (MAL-2025-191380) that steals credentials and exfiltrates sensitive data (malicious versions 1.1.4, 1.1.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @voiceflow/tsconfig-paths (npm)

MAL-2025-191380

Immediate action

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

npm uninstall @voiceflow/tsconfig-paths

What this malware does

The package @voiceflow/tsconfig-paths 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

1.1.41.1.5

Indicators of compromise (SHA-256)

4ae8285bace1b7f225c4c810422a0fdb90c0d9cc9ee378e19a1ecce545343c10

6fb7c02b11afed895db4edc03c6318bb09005f30253dcea72d4d1b0876478212

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @voiceflow/tsconfig-paths (2 malicious versions).
If you installed it — respond
@voiceflow/tsconfig-paths 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/tsconfig-paths 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/tsconfig-paths on npm has been identified as a malicious package (versions 1.1.4, 1.1.5 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/tsconfig-paths-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